1. All Collections >
  2. Integrations >
  3. Model Context Protocol (MCP)

Model Context Protocol (MCP)

Avatar
Joshua Lim
less than a minute read

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 the MCP server URL

  1. In your AI client, open the option to add a custom MCP server.

  2. Enter the respond.io MCP server URL: https://mcp.respond.io/mcp

  3. Sign in with your respond.io account when prompted.

  4. 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.

  5. Review the permissions listed, then click Allow.

Once authorized, you'll see a confirmation that the connection succeeded.

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
- Search and filter across all Contacts by criteria
- Create, update, or delete a Contact
- Manage tags and Lifecycle stages

Messaging

- Send messages, templates, and attachments
- Review message history and delivery status

Conversations

- Assign or unassign
- Open or close
- Add internal comments

AI Agents

- List, create, update, activate, deactivate, and delete AI Agents
- Enhance an agent's prompt
- Configure an agent's in-conversation actions

Workspace settings

- View team members, Channels, custom fields, and tags

Every action is scoped to what you're already allowed to do in respond.io.

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.

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.

What's next?

Share this article
Telegram
Facebook
Linkedin
Twitter

Can't find what you're looking for? πŸ”Ž