Freshdesk

What Freshdesk MCP server does

Freshdesk MCP server gives MCP-compatible clients read access to Freshdesk ticket and contact data through the Pipeworx gateway. Its ticket tools cover filtered lists, query-based searches, and complete records. Ticket details can include the subject, status, priority, description, conversations, attachments, and resolution notes.

Contact tools support customer lookup and inspection. Lists include identifying and filtering fields such as name, email, phone, company, and contact ID; an individual contact record can also include an address and ticket history.

The integration is an independent, unofficial connection to Freshdesk API v2. It is suited to support operations where an agent needs to answer questions from existing helpdesk records rather than create or modify them.

How it works

The hosted MCP endpoint is:

https://gateway.pipeworx.io/freshdesk/mcp

An MCP client connects to that URL and invokes the Freshdesk tools over the gateway. The endpoint also exposes shared Pipeworx meta-tools, including ask_pipeworx, discover_tools, search_within, and remember/recall. These additional tools are available alongside the pack tools and allow questions to be routed across the wider Pipeworx catalog.

A full gateway connection is also available at https://gateway.pipeworx.io/mcp. Both endpoints use the same gateway and data sources; the scoped endpoint lists the Freshdesk pack directly, while the full endpoint lists all packs directly.

Setup and configuration

Add the hosted endpoint to an MCP client configuration:

{
  "mcpServers": {
    "freshdesk": {
      "url": "https://gateway.pipeworx.io/freshdesk/mcp"
    }
  }
}

The package @pipeworx/mcp-freshdesk provides a local stdio bridge that forwards calls to the same hosted endpoint. Start it with npx:

{
  "mcpServers": {
    "freshdesk": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-freshdesk"]
    }
  }
}

The bridge requires network access. Without a Pipeworx key, anonymous use is limited to 50 calls per day. A free Pipeworx account raises the allowance to 200 calls per day; configure its key with PIPEWORX_API_KEY. Set PIPEWORX_META_TOOLS=1 when the local bridge should list the shared gateway tools as well as the Freshdesk tools.

Tools and capabilities

• freshdesk_list_tickets filters tickets by status and priority and returns ticket ID, subject, status, priority, and requester.
• freshdesk_get_ticket retrieves a complete ticket record, including conversations, attachments, and resolution notes.
• freshdesk_search_tickets searches by query syntax or keyword text, with examples including status:2 AND priority:3.
• freshdesk_list_contacts returns customer contacts with pagination and filtering fields.
• freshdesk_get_contact retrieves contact details, address information, and ticket history.
• ask_pipeworx can route plain-language questions across the wider Pipeworx catalog when the shared meta-tools are enabled or when using the hosted endpoint.

Limitations and notes

The listed Freshdesk tools are read-oriented: they list, search, and retrieve tickets and contacts, with no ticket or contact creation and mutation tools described. The npm bridge has no offline mode because it forwards requests to the network endpoint. Hosted and local calls are metered through Pipeworx, and the gateway's tool list can include roughly 30 shared tools in addition to the pack's own tools. Behind an HTTPS proxy, newer Node.js releases may require NODE_USE_ENV_PROXY=1 for the built-in fetch implementation to honor the proxy environment.