Files
freshservice-claude/mcp-server
spencerm 0b6747812f Handle custom ticket statuses: list_ticket_statuses tool + unresolved shortcut
The pesco instance defines 13 ticket statuses, not the 4 defaults, so a
(status:2 OR status:3) 'open tickets' filter silently dropped Working,
Scheduled, Waiting*, Pending Approval, etc. — undercounting 24 open tickets as 1.

Add a status helper that reads the status field from /ticket_form_fields and
treats only ids 4/5 (and closed/resolved-labelled) as terminal. Expose
list_ticket_statuses() and a list_tickets(unresolved=True) shortcut that builds
the full non-terminal status clause automatically. Document the gotcha in the
skill reference.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-16 21:36:25 -06:00
..

Freshservice MCP server (for Cowork / Claude Desktop)

Cowork runs the agent inside an isolated VM, so a locally-installed skill can't see your credentials or reach your Freshservice host. This MCP server runs as a container on the LAN box (192.168.101.12) — outside the VM — and Claude Desktop connects to it through mcp-remote, exactly like the existing sharepoint-lists server. Credentials and network both live on the LAN box.

(The skill in the parent directory remains the right tool for the Claude Code CLI, which is not sandboxed.)

Deploy on 192.168.101.12

# on the LAN box, in this directory
cp .env.example .env
# edit .env: FRESHSERVICE_DOMAIN, FRESHSERVICE_API_KEY, MCP_AUTH_TOKEN
#   token:  openssl rand -hex 32
docker compose up -d --build
docker compose logs -f          # confirm it started on :3838 inside the container

The container listens on container port 3838, published to host port 3839 (3838 is used by sharepoint-lists). Adjust in docker-compose.yml if needed.

Verify

# from the LAN box or any host that can reach it:
curl -s -o /dev/null -w "%{http_code}\n" -X POST \
  http://192.168.101.12:3839/mcp \
  -H "Authorization: Bearer <MCP_AUTH_TOKEN>" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"t","version":"0"}}}'
# expect 200 (401 means bad/missing token)

Connect Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json under mcpServers (alongside sharepoint-lists):

"freshservice": {
  "command": "/opt/homebrew/bin/npx",
  "args": [
    "-y", "mcp-remote",
    "http://192.168.101.12:3839/mcp",
    "--allow-http",
    "--header", "Authorization:${MCP_AUTH_HEADER}"
  ],
  "env": { "MCP_AUTH_HEADER": "Bearer <MCP_AUTH_TOKEN>" }
}

Restart Claude Desktop. The Freshservice tools then appear in chat and Cowork.

Tools

Tickets (list_tickets, get_ticket, create_ticket, update_ticket, reply_ticket, add_note, list_ticket_conversations), assets (search_assets, get_asset, update_asset), people (find_requester, list_agents, list_groups, list_departments), change/problem/release (list_changes, get_change, create_change, list_problems, get_problem, list_releases, get_release), and freshservice_request for any other v2 endpoint.