Reply.io MCP server

Reply.io MCP Server

Connect Reply.io to your AI client and let it work across your team and workspace. reply.io · Documentation

Overview

A remote MCP server at mcp.reply.io that lets MCP-compatible AI clients — Claude, ChatGPT, Cursor, Codex, and more — work with your Reply.io CRM and AI SDR. One connection gives an agent a catalog of tools spanning contacts, sequences, inbox, tasks, analytics, and the AI SDR ("Jason"), so it can read and act on Reply data without making direct HTTP requests. The tools run the same logic as the Reply.io API and the in-app AI assistant.

No local installation required. Free for all Reply.io users.

📖 Full documentation: docs.reply.io/reply-mcp

Where this fits

Reply's agentic toolkit is three pieces. They are complementary, not alternatives:

MCP gives your agent tools. Skills give it judgement. Most setups want both; a shell-capable agent can do everything through the CLI alone.

The shortest path that works: install the CLI, reply auth login, reply skills install, then talk to your agent in plain words. MCP is optional — add it when your client has no shell.

Connect

Reply MCP is a remote server at https://mcp.reply.io. Authenticate with a scoped personal API key (recommended) or OAuth, then add it to your client.

Claude Code

claude mcp add --transport http reply-mcp https://mcp.reply.io \
  --header "Authorization: Bearer usk_...your_key..."

Desktop apps (Claude, ChatGPT)

Add Reply MCP as a remote / custom connector using the URL https://mcp.reply.io and authorize with OAuth.

Create and scope a key under Settings → API Key in your Reply.io dashboard.

Note: Passing credentials in the URL (for example ?apikey=...) is not** supported. Always authenticate with the Authorization header or OAuth.

• Full connection guide (Codex, mcp-remote proxy, OAuth): docs.reply.io/reply-mcp#connect
• Authentication & keys: docs.reply.io/reply-mcp#authentication

Authentication & scopes

Reply MCP authenticates as a single Reply.io user, via one of two methods:

• Personal API key (recommended) — passed as Authorization: Bearer . A personal key is scoped: you grant it only the permissions your agent needs, and it can call only the tools those permissions cover.
• OAuth — authorize directly from the client, no key to copy. OAuth grants the full tool catalog (all scopes).

Each tool requires a single scope such as contacts:read or sequences:operate; a key can call a tool only if it holds that scope. Act-on-behalf keys (Team and Organization keys) are not supported on this single-user connection.

See the full scope list at docs.reply.io/api-reference/authentication#scopes.

Tools

Shortened. The full README is on GitHub.