respond.io MCP server
23 operations0 webhooks
Manage contacts, send and read messages, assign and close conversations, and read workspace channels, templates and custom fields with respond.io.
Try respond.io with your agent
Connect respond.io, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in respond.io on my account, then run one read-only example and show me the result.
respond.io tools and triggers
Tools are what your agent can do in respond.io through Corsair's MCP server. Triggers are the respond.io events a routine can start from.
Contacts
- Add TagsWrite
Add tags to a contact
contacts.addTags
- ChannelsRead-only
List the channels a contact has interacted on, whose IDs a custom-payload message needs
contacts.channels
- CreateWrite
Create a contact at an identifier; respond.io needs processing time afterwards, so wait before acting on it
contacts.create
- DeleteDestructive
Delete a contact and its conversation history
contacts.delete
- Delete TagsWrite
Remove tags from a contact
contacts.deleteTags
- GetRead-only
Read one contact by id:, email: or phone: identifier, with its fields, tags, assignee and lifecycle
contacts.get
- LifecycleWrite
Move a contact to a lifecycle stage by name, or clear it with null
contacts.lifecycle
- ListRead-only
List contacts with an $and or $or filter over fields, tags and lifecycle, a free-text search, and cursor paging
contacts.list
- MergeDestructive
Merge two contacts by their IDs, setting the merged fields; the older contact stays and the other is removed
contacts.merge
- UpdateWrite
Update a contact's fields by identifier
contacts.update
- UpsertWrite
Create or update a contact in one call, which is the safe choice when you do not know whether it exists
contacts.upsert
Space
- Get UserRead-only
Read one workspace user by ID
space.getUser
- List ChannelsRead-only
List the messaging channels connected in the workspace
space.listChannels
- List Closing NotesRead-only
List the closing notes a conversation can be closed with, sorted by category
space.listClosingNotes
- List Custom FieldsRead-only
List the custom field definitions, whose types a contact write must match
space.listCustomFields
- List TemplatesRead-only
List the message templates of one connected channel
space.listTemplates
- List UsersRead-only
List the workspace users
space.listUsers
Messages
- CommentWrite
Add an internal comment to a contact, which the customer never sees
messages.comment
- GetRead-only
Read one message by id, with its delivery status and sender
messages.get
- ListRead-only
List a contact's messages, optionally mixing in its comments; keep paging until pagination.next is null, since a page can be empty with more to come
messages.list
- SendWrite
Send a message to a contact, on the last channel it used unless channelId is given; this reaches the customer
messages.send
Conversations
- AssignWrite
Assign a contact to a user, or unassign it by sending a null assignee
conversations.assign
- StatusWrite
Open or close a contact's conversation, optionally recording a closing note and summary when closing
conversations.status
Connect respond.io to Claude, ChatGPT or Cursor
- 1
Connect respond.io in Corsair
Add your respond.io API key once in Corsair. Corsair stores the credential encrypted and makes the respond.io API calls for your agent, so it never goes into a prompt or a config file. Connect respond.io
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs respond.io. On a ChatGPT personal plan, connect respond.io here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, respond.io's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/respondio, add the respond.io plugin, and connect with an API key. Then call methods like corsair.respondio.api.contacts.addTags() from your app. Corsair keeps each tenant isolated.
Yes. respond.io requires an API key from your respond.io account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit respond.io, GitHub, Notion, Stripe, and the rest. Trigger respond.io from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for manage contacts, send and read messages, assign and close conversations, and read workspace channels, templates and custom fields with respond.io. Common builds include sync jobs, admin tooling, and agents that call respond.io APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per respond.io API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/respondio in the open repo. When respond.io ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your respond.io data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store respond.io data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put respond.io on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive respond.io operations. You can change a link's mode at hub.corsair.dev/me.