Can Lyro create a HelpDesk ticket or change its status?

Not through this toolkit. Every action here reads: List Tickets retrieves tickets from a silo with cursor pagination, and the rest list agents, teams, views, rules, and account configuration. No create, assign, or status-change action is exposed, so Lyro answers from what the help desk holds and hands the conversation to an agent when it cannot resolve it.

Can Lyro reuse the replies our agents already approved?

List Canned Responses returns the predefined reply templates configured on the account. That lets an answer follow wording your team has already signed off, instead of a second script maintained somewhere Lyro can see but your agents cannot.

Does Lyro see the custom fields we added to tickets?

List Custom Fields returns every custom field defined on the account, which is what Lyro needs to interpret a ticket carrying account-specific data such as a plan code or an order reference rather than treating it as free text.

What does a HelpDesk licence cover, and how is it different from a subscription?

List Licenses returns the account configurations - subscription information, global settings, default team and template assignments, and detected languages - and most accounts have exactly one. List Subscriptions is the billing view: plan type, team or enterprise, and the number of paid agent slots, including expired and future ones.

Helpdesk MCP integration

Reads the ticket queue and saved views, reports agents, teams, and roles, and explains email routing, automation rules, and plan setup.

Connect Helpdesk See all integrations

14actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

List tickets
Lyro displays all tickets from a specified silo with cursor-based pagination. Support managers track queue status without navigating dashboards.
List agents
Lyro retrieves all support agents in the HelpDesk account. Administrators quickly confirm team roster and permissions.
View agent
Lyro loads comprehensive details for a specific agent in the HelpDesk system. Managers review agent performance metrics and configurations instantly.

See all 14 actions

How businesses use Helpdesk + Lyro

Each card is one request a support team gets, and the Helpdesk actions Lyro runs to close it.

See what is sitting in the queue right now
Lyro lists tickets from a silo with cursor-based pagination and sorting, checks the saved agent views a team filters by, and pulls the canned responses those tickets are usually answered with.
List TicketsList ViewsList Canned Responses
Answer who is on the team and what they can do
Lyro lists every agent with their role, team membership, and active status, returns one agent's full profile including their signature configuration, and reports how teams are organised for routing.
List AgentsView AgentList Teams
Explain how mail actually reaches the help desk
Lyro reports the configured email domains with their verification status and DNS records, the reply addresses tickets are answered from, and the trusted senders on the spam whitelist.
List Email DomainsList Reply AddressesList Trusted Emails
Report what the account is configured to do on its own
Lyro lists the automation rules in force, the webhooks receiving ticket events, and the subscriptions behind them with plan type and paid agent slots.
List RulesList WebhooksList Subscriptions

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 Helpdesk actions it has and picks the ones a request needs.

01
Connect Helpdesk
Authorize the Helpdesk 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 Helpdesk 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

Helpdesk · Lyro

Everything else about Helpdesk

Setup, permissions, and the limits of what Lyro can do inside Helpdesk.

Not through this toolkit. Every action here reads: List Tickets retrieves tickets from a silo with cursor pagination, and the rest list agents, teams, views, rules, and account configuration. No create, assign, or status-change action is exposed, so Lyro answers from what the help desk holds and hands the conversation to an agent when it cannot resolve it.

Every action available in Helpdesk

All 14 actions your agent can call on Helpdesk, straight from the live MCP connection.

List agents
Retrieves all support agents (team members) in the HelpDesk account.
List canned responses
List canned responses.
List custom fields
List all custom fields defined in the account.
List email domains
Lists all email domains configured for the HelpDesk account.
List licenses
Retrieves all licenses (account configurations) for the authenticated HelpDesk account.
List reply addresses
Lists all reply addresses configured in the HelpDesk account.
List rules
Retrieve a list of rules configured in the account.
List subscriptions
Lists all billing subscriptions for the HelpDesk account, including active, expired, canceled, and future subscriptions.
List teams
Lists all teams in the HelpDesk account.
List tickets
List all tickets from a specified silo with cursor-based pagination support.
List trusted emails
Retrieve a list of trusted email addresses or domains.
List views
List agent views.
List webhooks
Lists all configured webhooks for the HelpDesk account.
View agent
Retrieves comprehensive details for a specific agent in the HelpDesk system.