Connect Controller to your agents.

Choose an MCP connection, add a supported source, and make the first governed call through Controller.

Start with the job in front of you

Read straight through for a first deployment, or jump directly to the surface you are configuring.

Make the first call

Install Controller, add a source, connect an agent, and invoke one catalog tool.

Connect an MCP client

Choose Streamable HTTP or use the CLI bridge for a stdio-only client.

Bring an existing API

Discover OpenAPI, GraphQL, or remote MCP and add named connections.

Limit an agent's catalog

Create a toolkit endpoint from the exact connections an agent should see.

Control execution

Set policy, approval, credential, and API-key boundaries around every call.

Operate Controller

Choose storage, configure secrets and authentication, then wire health probes.

Use the right surface

REST routes under /api/* manage integrations, connections, toolkits, policies, approvals, members, API keys, and settings.

MCP and the CLI are the execution surfaces for agents. Start with the MCP client guide when you are ready to connect one.

  • * Use the console or REST API to configure the workspace.
  • * Use MCP or the CLI to discover and execute catalog tools.
  • * Keep connection credentials behind Controller; agents receive results, not stored secrets.