OpenAssistantAPI
→

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 and manage tasks, read your calendar, search contacts, work with your files, memories and inbox, and more — the same set of things the CLI can do, acting as you and limited to what you approve.

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. An account admin turns it on for the account. Once enabled, you get a server URL scoped to your account — for this account, that's:

https://mcp.agnt.ai/agnt/mcp/openassistant

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). The client registers itself automatically, then sends you to a consent screen where you sign in and approve access. The screen summarizes what the client is asking for, with an expandable list of the individual permissions.

Access is scoped: each permission is a read or write pair for one area (tasks, calendars, contacts, memories, drive, and so on), so a client only gets what you approve. Access tokens are short-lived and refreshed automatically, and you can revoke a client's access at any time.

What tools show up

The tools an MCP client sees cover your account's resources — tasks, assistants, chats, contacts, calendars, connections, memories, skills, drive files, and more — limited to the permissions you granted.

Going the other way

This guide is about connecting an outside AI client to your assistant. To let your assistant use a third-party MCP server as a tool instead, add it as a connection — paste the server's URL when adding a connection and it's set up for you. See Connections.

Disconnecting

An account admin can turn MCP off, which disables the server for the whole account. A single client's authorization can also be revoked without affecting other connected clients.