Connect an agent
Point your agent at the gateway and start using tools
Agents connect to the gateway via MCP (Model Context Protocol). Once connected, they can access all tools from your configured resources — governed by your policies.
Register an agent
End users can self-onboard from the Quickstart page:
- Navigate to Quickstart in the sidebar
- Click your agent — Claude Code, Cursor, Copilot, Codex, and more
- Follow the setup steps in the dialog — each agent has its own configuration method
- Copy the token shown after the gateway provisions the instance
For agents not in the catalog, open Agents → Instances and click Add custom agent.
See the full setup guides for each supported agent:
Auto-registration
When an agent connects for the first time, the gateway automatically detects its type and records metadata like client name, version, and protocol version. The agent appears in the dashboard immediately.
Registry vs. Instances
Two views show the same agents from different angles:
- Agents → Registry — one card per agent type (Claude Code, Cursor, …) with aggregate instance counts and policy coverage. Use this to answer questions like which tools any Cursor instance can call across the org. See Agent Registry.
- Agents → Instances — every individual connected client across all users. Use this to debug a specific agent's identity, history, and effective access.
The instance detail page shows:
- Identity — user, client name and version, MCP protocol version
- Recent activity — audit events for this agent instance
- Effective access — which tools this instance can use based on current policies
Authentication
The first time your agent tries to use a tool that requires authentication (for example, Slack), the gateway will prompt you with a link to connect your account. No upfront setup needed — see Connections for details.