Is the Freshservice MCP server free?

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

How do I connect Freshservice to Claude or Cursor?

Connect Freshservice in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

What can my agent do in Freshservice?

It can call 12 tools, including Create Ticket, Add Note to Ticket, Create Requester, and chain them with steps in other apps inside the same run.

Is it safe to let an agent call Freshservice?

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.

Freshservice MCP server

IT service management software for ticketing, asset management, and IT operations.

Freshservice is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Start building See the Freshservice integration

Tools: 12
Works with: Any MCP client
Auth: Custom auth
License: MIT, open source
Updated: August 2026

About the Freshservice MCP server

Connect Freshservice once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Freshservice and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Freshservice tools your AI can run

Once connected, your assistant can call any of these Freshservice actions by asking in plain language.

Create Ticket
Creates a new ticket in Freshservice.
16 fields
Add Note to Ticket
Adds a private or public note to an existing ticket.
3 fields
Create Requester
Creates a new requester (end user) in Freshservice.
8 fields
Request Ticket Approval
Requests approval for a ticket from a specified agent.
3 fields
Create Change
Creates a new change request in Freshservice.
17 fields
Update Change
Updates an existing change request in Freshservice.
18 fields
Delete Change
Deletes a change request from Freshservice.
1 field
Add Note to Change
Adds a private or public note to an existing change request.
3 fields
Create Change Task
Creates a new task on a change request in Freshservice.
8 fields
Update Change Task
Updates an existing task on a change request in Freshservice.
9 fields
Delete Change Task
Deletes a task from a change request in Freshservice.
2 fields
Custom API Call
Make a custom API call to a specific endpoint
10 fields

Triggers

Freshservice events your agent can watch

These start a run the moment something happens in Freshservice, so work gets picked up on its own.

New Ticket
Triggers when a new ticket is created in Freshservice.
Updated Ticket
Triggers when an existing ticket is updated in Freshservice.
New Requester
Triggers when a new requester (user) is created in Freshservice.
Updated Requester
Triggers when an existing requester is updated in Freshservice.
New Change
Triggers when a new change request is created in Freshservice.
Updated Change
Triggers when an existing change request is updated in Freshservice. Note: newly created changes may also fire this trigger because their updated_at matches created_at.
New Change Task
Triggers when a new task is created on a specific change request.
1 field
Updated Change Task
Triggers when a task on a specific change request is updated. Note: newly created tasks may also fire this trigger because their updated_at matches created_at.
1 field

Freshservice MCP, answered.

No. That is the point of it. One Activepieces server exposes Freshservice alongside every other piece you connect, so your client keeps a single connection.