Helpdesk
HelpDesk is a ticketing system designed to streamline customer support by organizing and managing inquiries efficiently.
Verdict
Common use cases
- Audit automation rules before a workflow change
- Pull agent availability during escalation planning
- Review canned responses for tone consistency
- Check custom field configs for reporting gaps
- Verify email domains after DNS updates
Integration
- Vendor
- Helpdesk
- Category
- other
- Auth
- API_KEY
- Tools
- 15
- Composio slug
helpdesk
Tools
- List Agents
Tool to list agents. Use when you need to retrieve all agents on the account.
- List Canned Responses
Tool to list canned responses. Use when you need to retrieve all predefined reply templates for tickets.
- List Contacts
Tool to list contacts. Use when you need to retrieve contacts with optional filters and pagination.
- List Custom Fields
Tool to list all custom fields defined in the account. Use when you need to view or manage custom fields. Only callable after authentication.
- List Email Domains
Tool to list email domains configured for the account. Use when you need to retrieve all configured email domains after authenticating.
- List Licenses
Tool to list all licenses for an account. Use when you need to retrieve license configurations.
- List Reply Addresses
Tool to retrieve reply addresses. Use when you need to fetch all configured reply email addresses.
- List Rules
Tool to retrieve a list of rules configured in the account. Use after authentication when you need an overview of all automation rules.
- List Subscriptions
Tool to list subscriptions. Use when you need to retrieve current or historical subscription details.
- List Teams
Tool to list all teams for the authenticated Helpdesk account. Use after providing valid credentials to retrieve team IDs, names, and settings. Example: "List all teams".
- List Tickets
Tool to list tickets with cursor-based pagination. Use when you need to fetch multiple pages of tickets after setting your cursor and sort parameters.
- List Trusted Emails
Tool to retrieve a list of trusted email addresses or domains. Use when managing your spam whitelist after authenticating.
- List Views
Tool to list agent views. Use when you need to retrieve saved ticket views after authentication.
- List Webhooks
Tool to list all webhooks configured for events. Use when you need to retrieve webhook configurations for an account.
- View Agent
Tool to retrieve details of a specific agent (v1). Use after confirming agent ID.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select Helpdesk from the list. 3. Log into your Helpdesk account in a separate tab and go to Settings > API Keys. 4. Generate a new API key with read permissions for tickets, contacts, and configuration data. 5. Copy the key and paste it into the API Key field in Switchy, then click 'Connect'. 6. Switchy will verify the connection by fetching your account's agent list. 7. Open any Space, type '@Helpdesk list agents' in the chat, and hit send — if you see your team roster, the integration is live. 8. To test further, try '@Helpdesk list canned responses' to confirm template access works.
What teammates see: by default, memories from Helpdesk are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Agent Roster Check
@Helpdesk list all agents on the account and show their current statusOpen in a Space →
Canned Response Audit
@Helpdesk list all canned responses and group them by category or use caseOpen in a Space →
Custom Field Inventory
@Helpdesk list all custom fields and describe what each one tracksOpen in a Space →
Email Domain Review
@Helpdesk list all email domains configured for this accountOpen in a Space →
Automation Rule Summary
@Helpdesk list all rules and summarize what each one does in plain languageOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Helpdesk show me all open tickets from contacts at acme.com that haven't been updated in the last 3 days
Based on the Helpdesk account data, there are 7 open tickets matching those filters. For example: Ticket #4521 from sarah.chen@acme.com (subject: 'Login issues on mobile app') last updated 4 days ago, assigned to Agent Mike Torres. Ticket #4498 from john.park@acme.com (subject: 'Billing discrepancy Q1') last updated 5 days ago, unassigned. The full list includes ticket IDs, contact names, subjects, assigned agents, and days since last activity. This illustrative example shows how the MCP combines contact filtering with ticket status queries.
This example demonstrates read-heavy operations combining List Contacts and ticket filtering. Requires API key with read access to both tickets and contacts. Response time depends on account size — accounts with 10k+ tickets may see slower queries. No side effects; purely informational.
@Helpdesk create a new ticket for emma.rodriguez@techcorp.io with subject 'API rate limit errors' and assign it to the agent handling integrations
Ticket #4589 created successfully for contact Emma Rodriguez (emma.rodriguez@techcorp.io). Subject set to 'API rate limit errors'. The ticket has been assigned to Agent Lisa Kim, who is tagged with the 'integrations' specialty in your agent roster. Ticket is now in 'Open' status with normal priority. A confirmation email was sent to the contact's address. This illustrative example shows the MCP's ability to create tickets and route them based on agent metadata.
This example showcases ticket creation with intelligent agent assignment. Requires API key with write permissions for tickets. Creates a real ticket in your Helpdesk account — use cautiously in production Spaces. The MCP must first query List Agents to match the 'integrations' criteria, then execute the create action.
@Helpdesk review all automation rules currently active and summarize which ones might be causing tickets from VIP contacts to skip the priority queue
After reviewing the 12 active automation rules in your account, two rules may affect VIP contact prioritization: Rule #7 ('Auto-assign by domain') triggers on all @enterprise.com emails and assigns to the general pool, potentially overriding VIP flags. Rule #11 ('Weekend ticket routing') redirects Saturday/Sunday tickets to a separate queue regardless of contact status. The remaining rules focus on tagging, canned responses, and SLA timers without priority conflicts. This illustrative analysis combines rule metadata with logical inference about workflow impact.
This example pairs the MCP's List Rules capability with the AI's reasoning to diagnose workflow issues. Read-only operation; no changes made to rules. Effectiveness depends on how descriptive your rule names and conditions are in Helpdesk. The AI infers potential conflicts but cannot test rule execution without live ticket data.
Use-case deep-dives
When this MCP works for onboarding new support reps
A 6-person support team onboarding two new hires needs to document their canned responses, custom fields, and routing rules without screen-sharing through the Helpdesk UI. This MCP is the right call. The new reps can ask Switchy to list all canned responses by category, pull the custom field definitions they'll use for ticket tagging, and review the automation rules that route tickets to their queue. The API key auth means setup takes under two minutes. The threshold: if your team changes canned responses daily or runs complex multi-step workflows, you'll want a dedicated knowledge base instead of querying the MCP each time. For stable onboarding docs that pull live data, this is faster than maintaining a stale wiki.
When this MCP wins for pre-migration inventory
A 12-person SaaS company switching from Helpdesk to another platform needs a complete export of their support configuration—agents, reply addresses, email domains, custom fields, and rules—to map into the new system. This MCP handles it in one session. The ops lead can ask Switchy to list all agents with their roles, pull every custom field definition, and dump the automation rules into a spreadsheet-ready format. The 15 tools cover the full config surface, so nothing gets missed in a manual export. The trade-off: if you need historical ticket data or attachment files, this MCP doesn't touch those; you'll need Helpdesk's native export for that. For configuration inventory before a cutover, this is the cleanest path.
When this MCP falls short for ongoing analytics
A 4-person support team wants to review agent performance and ticket volume trends every Monday standup. This MCP isn't the right fit. It lists agents and contacts, but it doesn't expose ticket counts, response times, or resolution metrics—the tools are config-focused, not analytics-focused. You can pull the list of agents and see who's active, but you can't answer 'how many tickets did each agent close last week' without a separate reporting tool. The threshold: if your review is about configuration changes (new canned responses added, rules updated), the MCP works. If you're tracking KPIs, you need Helpdesk's native reports or a BI connector. For config audits, yes; for performance dashboards, no.
Frequently asked
What does the Helpdesk MCP do in Switchy?
It connects your Helpdesk account so AI agents can read ticket data, pull canned responses, check agent assignments, and review automation rules. The MCP can't create or update tickets — it's read-only access to your support configuration and contact lists. Use it when you need AI to reference support context without switching tabs.
Do I need admin access to connect Helpdesk MCP?
You need an API key from your Helpdesk account, which typically requires admin or owner permissions to generate. The key authenticates all 15 tools, so whoever connects it should have visibility into agents, custom fields, and automation rules. Check your Helpdesk account settings under API or Integrations to create the key.
Can the Helpdesk MCP reply to tickets or assign them to agents?
No. The MCP only reads data — it lists agents, contacts, canned responses, rules, and custom fields. It can't send replies, change ticket status, or reassign conversations. If you need to act on tickets, use Helpdesk's web app or a webhook-based automation tool alongside this MCP for context retrieval.
Why use this MCP instead of logging into Helpdesk directly?
The MCP lets AI pull support data into your Switchy workspace without copy-pasting between tabs. If you're drafting a response that references a canned reply template or checking which agent handles a domain, the AI fetches it inline. For ticket triage or updates, you still need the Helpdesk UI.
Who on the team should connect the Helpdesk MCP?
Whoever manages your Helpdesk API keys — usually a support lead or IT admin. Once connected in Switchy, any workspace member can ask AI to query agents, contacts, or rules. The connection doesn't consume Helpdesk seats, but the API key grants read access to all account data, so treat it like a credential.