Freshdesk MCP Server

An MCP server for the Freshdesk API v2. It lets an AI agent search and read tickets and their conversations, contacts, companies, agents, groups, the knowledge base (solutions), SLA policies, business hours and canned responses and, on explicit request, create and update records, reply to tickets, add notes and (with confirmation) delete, merge or convert records.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored; every tool is listed from the first tools/list

• Python 3.12, uv, FastMCP, httpx

• License: Apache-2.0, Copyright 2026 MSPbots.ai

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: Zendesk MCP Server

Authentication headers

Where to get them: the subdomain is the yourcompany in https://yourcompany.freshdesk.com. The API key is under Profile settings -> View API Key of the agent whose permissions the agent should have; every action is performed, and audited, as that agent.

How the key is sent to Freshdesk: every call goes to https://{subdomain}.freshdesk.com/api/v2/... with HTTP Basic authentication (the API key as user name, X as password). Only freshdesk.com accounts are accepted, so the key is never sent to another host.

A request to /mcp without both headers gets HTTP 401 naming the missing one; a domain that is not a Freshdesk account gets HTTP 400.

Tools

All tools return a JSON string. List tools take page and perPage (max 100) and return {count, page, has_more, next_page, offset, next_offset}. They also take offset (record position, overrides page): a page cut to fit the response size limit has no other page holding its rest, so next_offset starts right after the last record returned; pass it as offset to continue without gaps. Search tools return 30 results per page for at most 10 pages (300 results). Search tools also take offset (0-299) and return next_offset: when a page is cut to fit the response size limit, next_offset starts right after the last result returned, so pass it as offset to continue without gaps. Empty values are left out of search results. A record too large on its own (e.g. a ticket with a long HTML description) comes back with long fields shortened and fields_truncated: true; freshdesk_tickets_get shortens the HTML description first and keeps description_text. Freshdesk has no endpoint for one conversation: to read a long one in full, call freshdesk_tickets_list_conversations with perPage: 1 and page: N. Ticket status: 2 Open, 3 Pending, 4 Resolved, 5 Closed; priority: 1 Low, 2 Medium, 3 High, 4 Urgent. write marks tools that change data; confirm marks tools that also need confirm: true.

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "invalid_argument", "message": "Freshdesk returned HTTP 400 for contacts: Validation failed - email: It should be a valid email address", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error; Freshdesk's per-field validation messages are kept. Reads are retried with backoff on 429, 5xx and network errors; writes only on 429 (honouring Retry-After). Freshdesk limits API calls per minute according to the plan.

Run locally

uv sync
uv run python -m freshdesk_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t freshdesk-mcp:dev .
docker run --rm -p 8080:8080 freshdesk-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Freshdesk-Domain: yourcompany" \
  -H "X-Freshdesk-Api-Key: your-freshdesk-api-key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# open urgent tickets
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Freshdesk-Domain: yourcompany" \
  -H "X-Freshdesk-Api-Key: your-freshdesk-api-key" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"freshdesk_tickets_search","arguments":{"query":"status:2 AND priority:4"}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Tool count (66). Kept as is because the tool names are an existing contract; every tool is listed from the first tools/list.

• Confirmation for irreversible actions. Older versions asked the user to confirm deletes mid-call and carried on when the client could not show the prompt, which is always the case behind a stateless gateway. The 12 delete / merge / make-agent tools now need confirm: true and otherwise return a "not done" result describing the action.

• Fixes against the Freshdesk API reference. freshdesk_contacts_send_invite now uses PUT (the documented method); freshdesk_agents_create sends the agent type as Freshdesk's numeric agent_type (support_agent 1, field_agent 2, collaborator 3) instead of an unknown type field.

• Search. Queries are wrapped in the double quotes Freshdesk requires; string values inside take single quotes (tag:'vip').

• Notes default to private; replies email the requester, which the description states.

License

Apache License 2.0 - see LICENSE and NOTICE.