MCP overview

MCP is Slab5's agent interface for connecting AI clients to workspace tools. Tools expose business actions, not raw database access.

Use MCP when you are connecting an agent. Use REST when you are building an app. MCP tools and REST routes operate on the same workspace data, scopes, module enablement, audit events, usage events, and structured errors.

Slab5 can also connect to external MCP servers from AgentGrid. External MCP tools are discovered live, reviewed by workspace owners, risk-scored, and executed through Slab5 policy checks before AgentGrid or App Studio can use them. See External MCP tools for the owner approval and execution model.

Tool design

Every tool has an input schema, output schema, required scopes, request ID, clear errors, audit logging, usage metering, idempotency guidance, and an API equivalent. The gateway executes initialize, ping, tools/list, and tools/call against the same app-plane services used by REST.

Hosted clients can discover the MCP server through the production /v1 endpoint and OAuth protected-resource metadata. Workspace selectors such as workspace_id and workspace_slug are routing context only and must not contain secrets.