Skip to main content
Gradient hosts a remote Model Context Protocol server on the console. Point an MCP client at it with an organization API key and a coding agent can build agents, deploy and call tools, manage knowledge bases and phone numbers, run dataset SQL, and author red-team and rubric experiments, the same operations the dashboard exposes.
The transport is Streamable HTTP. The server exposes tools (no separate resources).

Connecting

Authenticate with Authorization: Bearer grad_live_..., an organization API key from the console. The server verifies the key, then enforces the matching scope on each tool it runs, so a key scoped to agents:* and tools:* can build and deploy but not, say, manage providers. See Authentication for scopes.
For clients that speak Streamable HTTP directly, such as Claude Code and Cursor:

Tool surface

Identity

Agents

Graph editing

Each of these acts on an agent’s draft graph.

Publish and run

Skills

Knowledge bases

Custom tools

Providers

Phone and voice

Dataset worlds

Evaluation and observability

Each tool returns its result as JSON text; very large payloads are truncated with the original size noted. For how these operations fit the build-and-evaluate loop, see Run over MCP.