Skip to content
Freshdesk logo

Freshdesk MCP server

Customer support software

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

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

About the Freshdesk MCP server

Connect Freshdesk 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 Freshdesk and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Freshdesk tools your AI can run

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

  • Get Tickets

    Get Ticket instances from Freshdesk.

  • Get Contact from ID

    Get contacts details from Freshdesk using ID number.

    1 field

  • Get Ticket Status

    Get Ticket status from Freshdesk. Returns ticket_status, assigned_status, assigned_id

    1 field

  • Get Freshdesk Contacts

    Get contact details from Freshdesk for all (optional filtered) contacts.

    4 fields

  • Get All Tickets By Status

    Get All Tickets by selected status from Freshdesk.

    1 field

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Freshdesk MCP, answered.

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

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.

Connect Freshdesk 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.

It can call 6 tools, including Get Tickets, Get Contact from ID, Get Ticket Status, and chain them with steps in other apps inside the same run.

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.