Skip to main content
The platform exposes its own capabilities as MCP tools, so a model or an assistant can operate it directly rather than through generated HTTP calls. This page covers what is on that surface, how to narrow a connection to the part you want, and how a tool call is authorized. It is the mirror image of the MCP Gateway, which is the path for exposing your tools to agents.

​
The two MCP surfaces

Getting these the right way round matters:

​
What is on it

Entries are tools, resources, and prompts, grouped into toolsets by the job they do:

​
Scoping a connection

By default a connection serves everything. Two query parameters subtract from that:
Scope deliberately. A model given the whole surface spends context on tool descriptions it will never call, and a narrow connection is both cheaper and easier to reason about. Point an assistant at the toolsets its job needs.

​
Knowing which workspace you are in

One tool is always served regardless of scoping: whoami. A connection is bound to exactly one workspace, nothing else on the surface reports which, and an assistant asked “which workspace am I operating in?” would otherwise have no way to answer. It returns the active workspace, the acting identity, and — for a person — every workspace they belong to, with the current one marked.

​
Authorization

Every tool call is checked against the same capability as its HTTP equivalent. There is no shortcut here: an assistant connected as you can do what you can do, and nothing more.
Authorization depends on the arguments, not only on the tool. A general-purpose tool resolves to different capabilities depending on what it is asked to act on, so being able to call a tool is not the same as being able to do everything it can express.
Guardrails apply to this surface as well as to the gateway: a rule at the tool-call gate covers both your own connected servers and the platform’s own tools. See Standards & Guardrails.

​
Next steps

Connect coding agents

Wiring Claude Code, Codex CLI, or Cursor to this surface.

MCP Gateway

The other direction — your tools, for your agents.

Roles & permissions

The capabilities a tool call is checked against.

APIs

The same capabilities over HTTP.