Developer Platform

MCP tools for AI clients

Expose approved API-backed application capabilities to MCP-compatible AI clients under the same permission envelope.

Model Context Protocol (MCP) gives AI clients a standard way to discover and call tools. BuildWithHQ's opportunity is to generate those tools from the application capabilities that already exist instead of maintaining a separate AI-only integration layer.

What becomes a tool

An application's MCP catalog can be assembled from approved capabilities such as:

• permission-aware record search and retrieval;
• safe record actions and registered data operations;
• published workflows that are allowed to be started by the caller;
• approved container/appliance endpoints with declared schemas; and
• AI-specific actions that are explicitly enabled for the user's role.

Generated, not privileged

MCP is a protocol adapter over the same application service layer used by REST. Tool discovery itself is filtered: if an identity cannot invoke a capability, that capability is not offered.

Current endpoint

The stateless Streamable HTTP endpoint is /v1/apps/{saasAppId}/mcp. The API credential must carry mcp.use plus the ordinary scope required by each discovered tool, such as records.read, webhooks.write, or appliances.invoke.

Tool contracts

Each tool needs a stable name, description, JSON input schema, output schema, required permission, side-effect classification, and — for sensitive mutations — an approval policy. Read tools and write tools should be visibly distinguishable to both AI clients and users.

Auditability

Every mutation performed through MCP should carry correlation and actor context into the normal application audit path. For container-backed tools, the platform can also record the resolved endpoint identity and invocation outcome so an administrator can explain what code actually ran.