The respond.io MCP server lets AI assistants, such as Claude or ChatGPT, act on your Workspace using natural language. The hosted MCP server runs on respond.io's own infrastructure. It authorizes access with OAuth, so you don't install anything, host anything, or share a credential.
Before you begin
You need a respond.io account with access to the Workspace you want to connect.
The connection only exposes what your respond.io user role already allows. Connecting an AI assistant does not grant it any additional access.
Connect with a native connector
In your AI client, open its connector or plugin directory and select respond.io.
Sign in with your respond.io account when prompted.
On the Connect with respond.io MCP screen, select the Workspace to authorize. If you only have access to one Workspace, it's selected automatically.
Review the permissions listed, then click Allow.
Once authorized, check whether the connection was successful in your AI client.
Connect with the MCP server URL
Some AI clients don't yet list respond.io as a native connector. Add the connection manually instead:
In your AI client, open the option to add a custom MCP server.
Enter the respond.io MCP server URL:
https://mcp.respond.io/mcpSign in and authorize the connection the same way as the native connector flow above.
What the hosted MCP server supports
Once connected, your AI assistant can work with:
Category | What you can do |
|---|---|
Contacts | - Look up a specific Contact by ID, email, or phone |
Messaging | - Send messages, templates, and attachments |
Conversations | - Assign or unassign |
AI Agents | - List, create, update, activate, deactivate, and delete AI Agents (deleting reassigns the agent's Contacts) |
Workspace settings | - View team members, teams, Channels, and Lifecycle stages |
Workflows | View Workflows, including their status and settings |
Your account | View your profile and the Organizations and Workspaces you have access to |
Every action is scoped to what you're already allowed to do in respond.io.
Managing AI Agents through MCP
Two of these capabilities change an AI Agent's setup rather than a live conversation. Ask your AI assistant for either one in plain language.
Enhance an AI Agent's prompt
This returns an AI-improved version of an existing prompt. The result is a suggestion — your AI Agent keeps its current prompt until you apply the change.
Example: "Enhance the instruction section of this prompt."
Configure in-conversation actions
In-conversation actions are the platform actions an AI Agent takes while it replies to a Contact. Configuring them sets which actions the AI Agent is allowed to use.
Example: "Set up my support agent to close conversations, assign to Sales, update the Lifecycle stage and Contact fields, add tags, trigger my follow-up Workflow, and add comments."
For the full list and how each action behaves, see Using AI Agent Actions.
Managing your connection
Each connection is authorized for one Workspace. To connect a different Workspace, reconnect and select it during sign-in.
Permissions update immediately if your respond.io role changes or your Workspace access is removed. No separate token exists to expire or revoke.
FAQ and troubleshooting
Can I still use the local, self-hosted MCP server?
Yes. The self-hosted setup is unchanged and continues to work with a Developer API token. See the respond.io MCP developer documentation for those steps, or Developer API for how to generate a token.
Does connecting an AI assistant give it more access than I have?
No. Every action is limited to your existing respond.io permissions.
Can I connect more than one Workspace at once?
No. Each connection covers one Workspace — reconnect to switch.
Does enhancing a prompt update my AI Agent?
No. The action returns a suggestion only. Your AI Agent keeps its current prompt until you apply the change.
What happens if the connection fails?
You'll see a screen stating the connection wasn't established, with a reason for the failure. Close the tab and try connecting again.
