MCP server

Connect Claude, Cursor, or any MCP-compatible client directly to your assistant.

What this gives you

Your account can expose its own MCP server — a standard interface that lets AI clients like Claude, Claude Code, and Cursor call your assistant's tools directly, instead of going through the chat UI. Once connected, an MCP client can create tasks, read your calendar, search contacts, and use anything else your assistant's installed skills expose — using the same permissions as if you'd asked in a normal conversation.

This is different from using the API directly: MCP is built for AI clients that speak the protocol natively, so you don't write any integration code — you just add a server URL to the client's config.

Enabling it

MCP is off by default. Turn it on from your account's settings. Once enabled, you get a server URL scoped to your account — for this account, that's:

https://mcp.agnt.ai/agnt/mcp/your-account

Connecting a client

Add the server URL to your MCP client's configuration (the exact steps vary by client — Claude Desktop, Claude Code, and Cursor all support MCP servers via their own settings). You'll be prompted to authorize the connection the first time, the same OAuth-style flow you'd use to connect any other integration — see Connections.

What tools show up

The tools an MCP client sees mirror whatever skills are installed for you — if you don't have a calendar skill installed, an MCP client won't see calendar tools either. Installing or removing a skill changes what's available over MCP immediately, no reconnection needed.

Disconnecting

Turn MCP off from the same settings section to revoke the server entirely, or disconnect an individual client's authorization from Connections without disabling MCP for everyone else who's connected.