KonvoAI Docs
MCP server

Enabling MCP

Enable the KonvoAI MCP server for your user account and connect a client.

Enable in KonvoAI

  1. Open Settings → Advanced in the KonvoAI web app.
  2. Turn on Enable MCP server.
  3. Copy the Server URL shown on the page (for example https://api.konvoai.com/mcp).

MCP access is per user. The connected client acts as you across every organization you belong to (excluding partner-only memberships).

Add to the Claude app

Most users connect through Claude's Connectors, not by editing JSON. In the Claude app (web or desktop), open Settings → Connectors, choose Add custom connector, and paste your Server URL. Claude runs the OAuth sign-in for you.

The Advanced settings page also shows an Add to Claude button that opens this dialog with the URL pre-filled. On Team and Enterprise plans an Owner adds the connector once under Admin settings → Connectors; members then click Connect.

Connect Claude Code

With MCP enabled, the Advanced settings page shows a JSON snippet for Claude Code. It registers an HTTP MCP server named konvoai:

{
  "mcpServers": {
    "konvoai": {
      "type": "http",
      "url": "https://api.konvoai.com/mcp"
    }
  }
}

Replace the URL with your environment's API origin when developing locally.

On first use, Claude Code discovers OAuth metadata from the server, opens a browser sign-in through WorkOS AuthKit, and stores an access token scoped to the MCP resource.

Changing the organization

When you authorize an MCP client, WorkOS asks which organization to connect. That choice is stored in your authorization grant — removing and re-adding the connector in your MCP client alone does not change it.

To connect to a different organization:

  1. Open Settings → Advanced in the KonvoAI web app.
  2. Click Reset MCP authorization and confirm.
  3. In your MCP client, remove the KonvoAI connector and add it again.
  4. Sign in when prompted and select the organization you want.

Disable access

Turn off Enable MCP server in Advanced settings. Existing OAuth tokens stop working on the next request because the server rejects MCP calls for disabled users.

On this page