Respond.io MCP integration
Creates contacts from a first-touch conversation, leaves internal notes for the next agent, and maintains the workspace tag list.
7actions available
Three actions you can hand over today
Every action runs live through MCP. Nothing to build, nothing to maintain.
Add internal comment to conversation
Lyro attaches a private note to a customer conversation. Team members communicate context without alerting the customer.
Create contact
Lyro adds a new contact to the Respond.io workspace. Support teams register customers for follow-up.
Update space tag
Lyro modifies a tag used to organize conversations. Support teams refine categorization as workflow needs shift.
How businesses use Respond.io + Lyro
Each card is one request a support team gets, and the Respond.io actions Lyro runs to close it.
Create the contact behind a new conversation
Lyro reads the message that opened the thread, checks which connected channel it arrived on, and creates the Respond.io contact from the email or phone number it came from.
Create ContactGet MessageList ChannelsLeave the handover note on the conversation
Before a thread reaches an agent, Lyro posts an internal comment summarising what the customer asked and what has already been checked, so the agent does not re-read the whole exchange.
Add Internal Comment to ConversationGet MessageKeep the workspace tag list usable
Lyro adds the tag a new segment needs and renames or re-describes ones that have drifted, so filtering and workflow automation keep working off a vocabulary people recognise.
Create Space TagUpdate Space TagAnswer who and what a workspace covers
Lyro enumerates the messaging channels connected to the workspace and the users in it, so a routing or coverage question is answered from the live configuration.
List ChannelsList Users
How it works
Get started in 3 steps
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Respond.io actions it has and picks the ones a request needs.
- 01
Connect Respond.io
Authorize the Respond.io account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
- 02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Respond.io actions that close it and chains as many as the request needs.
- 03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free
Everything else about Respond.io
Setup, permissions, and the limits of what Lyro can do inside Respond.io.
Not with this toolkit. It exposes Get Message for reading a single message and Add internal comment to conversation for notes, but no outbound send action. Lyro answers the customer in its own channels and leaves the Respond.io thread annotated for the agent who takes it.
Every action available in Respond.io
All 7 actions your agent can call on Respond.io, straight from the live MCP connection.
Add internal comment to conversation
Add a comment (internal note) to a contact's conversation.
Create contact
Creates a new contact in the respond.io workspace with the specified details.
Create space tag
Creates a new tag in the Respond.io workspace for organizing and categorizing contacts and conversations.
Get message
Retrieve a specific message.
List channels
Retrieve a list of channels connected to the workspace.
List users
Retrieve a list of users in the workspace.
Update space tag
Updates an existing workspace tag by its current name.
The tools Respond.io sits next to
Same connection, same setup. Pick the next one your team already uses.
Docsbot.ai
Searches an indexed documentation base for grounded answers, keeps its sources re-indexed, and escalates the questions it cannot close.
Helpdesk
Reads the ticket queue and saved views, reports agents, teams, and roles, and explains email routing, automation rules, and plan setup.
Landbot
Messages known customers, filters who has interacted by channel or opt-in, and keeps agent availability and brand data current.
Re amaze
Reads approved response templates and report tags so replies use your team's own wording and categories, not a separate script.
Sitespeakai
Lists the chatbots on an account, retrieves the leads they captured, and reads the smart prompts configured on a given bot.
Zendesk
Looks up ticket history, opens and replies to tickets, and keeps the queue tagged and deduplicated without an agent stepping in.
Ready to connect Respond.io?
Authorize the account and your agent has all 7 actions from the first conversation.