Connect your AI Agents to Freshservice in minutes

What is a Freshservice MCP?

It's an MCP server that routes your agents directly into Freshservice's IT service management platform via tools. Your agents can invoke these tools to create and update tickets, manage IT assets, log change requests, add notes to incidents, and more.

Freshworks doesn't offer an MCP server purpose built for Freshservice, but you can use one from a third-party platform, like Merge Agent Handler.

How can I use the Freshservice MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Auto-ticket creation from monitoring alerts: When an alert fires in a tool like Datadog or PagerDuty, an agent creates a Freshservice ticket with the error details pre-populated, sets the appropriate priority, and assigns it to the on-call engineer automatically

• Ticket triage from Slack: A Slack-based agent monitors a support channel and when a user reports an issue, it creates a Freshservice ticket, links it to the requester's profile, and replies in the thread with the ticket number and status

• Change request logging for deployments: When a deployment is approved in a CI/CD pipeline, an agent opens a change request in Freshservice, fills in the deployment scope and rollback plan, and notifies the change advisory board

• Asset reclamation on offboarding: When an employee offboarding ticket is created in Freshservice, an agent looks up all assets assigned to that person in the CMDB and creates individual tasks to reclaim each device before the departure date

What are popular tools for Freshservice's MCP server?

Here are some of the most commonly used tools:

• create_ticket: opens a new service desk ticket with fields like subject, description, priority, and assignee. Use this when an agent needs to log an incident or request triggered by an event in another system

• update_ticket: modifies an existing ticket's status, priority, assignee, or custom fields. Good for workflows that need to escalate, reassign, or close tickets based on conditions evaluated outside Freshservice

• list_tickets: retrieves tickets filtered by status, priority, requester, or date range. Useful for agents that need to pull a queue of open incidents for triage or reporting

• add_ticket_note: appends a private or public note to an existing ticket. Call this when an agent gathers context from another tool and needs to document it against the ticket without changing its status

• create_change: opens a change request with fields for type, risk level, planned dates, and approvers. Use this when an agent detects an approved deployment or configuration change that needs to be tracked in the ITSM workflow

• list_assets: returns IT assets from the CMDB, filterable by type, status, or assigned user. Helpful when an agent needs to look up what hardware or software is tied to a specific employee or department

What makes Merge Agent Handler's Freshservice MCP server better than alternative Freshservice MCP servers?

There are a few clear advantages to running Freshservice through Merge Agent Handler rather than wiring it up directly or using a community server:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Freshservice, this means you can prevent ticket details, requester contact information, and internal IT notes from being exposed even when the agent has broad read access

• Managed authentication and credentials: Merge stores and refreshes Freshservice API credentials on your behalf. You never need to inject raw keys into an agent or rebuild your auth flow when credentials rotate

• Real-time observability and audit trail: Every tool call against Freshservice is recorded: timestamp, tool name, inputs, and response metadata. Your IT and security teams can audit exactly what the agent touched without adding any instrumentation to the agent itself

• Tool Packs and controlled access: Tool Packs let you bundle specific Freshservice tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Freshservice MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).

2. Create a new Tool Pack, then find and enable the Freshservice connector. Choose which tools to include: read tools like list_tickets and list_assets are enough for reporting and triage use cases, while write tools like create_ticket and update_ticket are needed if your agent should take action on service desk records.

3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.

4. From the Registered User detail page, authenticate Freshservice by entering your API credentials. Merge stores and manages those credentials going forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.

6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your Freshservice tools are now accessible through that endpoint.