Convot MCP Server

Give an AI agent the ability to operate a Convot inbox. The Model Context Protocol server wraps the REST API as a curated set of tools an agent can call directly - read and reply to conversations, manage contacts, and search your help center.

How it relates to the REST API

The MCP server is a thin client over the same Convot REST API documented here. Every tool maps to a single REST endpoint and uses the same API key, scopes, and rate limits. It exposes a focused "operate the inbox" subset - admin content CRUD, webhook subscriptions, and uploads stay REST-only, since those are app-to-app integrations rather than things an agent does.

Install

Nothing to clone or build - the server is published to npm and runs on demand via npx. All you need is Node.js 18+. Your MCP client (below) launches it for you; to run it standalone:

npx -y convot-mcp

Configure

Create an API key in the dashboard under App Settings → API Keys. It has the form prefix:secret and is scoped to one app.

Required scopes for the full tool set: conversations:read, conversations:write, messages:read, messages:write, contacts:read, contacts:write, helpdesk:read.

Connect your client

Claude Code

claude mcp add convot \
  --env CONVOT_API_KEY=prefix:secret \
  -- npx -y convot-mcp

Claude Desktop (and other MCP clients) - add to your config:

{
  "mcpServers": {
    "convot": {
      "command": "npx",
      "args": ["-y", "convot-mcp"],
      "env": { "CONVOT_API_KEY": "prefix:secret" }
    }
  }
}

Tools

These are generated from the API spec below - each tool is a Convot REST operation. See the REST reference for full parameter and response schemas.

Source of truth: the tool list is derived from openapi.yaml (operations tagged x-mcp-tool), so it never drifts from the REST API.