MCP server for Freshdesk (iplweb fork) - MCP Python SDK 2.x, extra CRUD, filtering and bulk-fetch tools
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"freshdesk-mcp-iplweb","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Freshdesk MCP Server (iplweb fork) [](https://pypi.org/project/freshdesk-mcp-iplweb/) [](https://pypi.org/project/freshdesk-mcp-iplweb/) [](https://github.com/mpasternak/freshdesk_mcp/actions/workflows/ci.yml) [](LICENSE) An MCP server implementation that integrates with Freshdesk, enabling AI models to interact with Freshdesk modules and perform various support operations. > This is a fork of [effytech/freshdesk_mcp](https://github.com/effytech/freshdesk_mcp), > published to PyPI as **`freshdesk-mcp-iplweb`**. It runs on the MCP Python SDK 2.x > and carries three pull requests still open upstream — 78 tools instead of 59. > See [What this fork adds](#what-this-fork-adds). Upstream remains the original > project; all credit for the server itself goes there. ## Features - **Freshdesk Integration**: Seamless interaction with Freshdesk API endpoints - **AI Model Support**: Enables AI models to perform support operations through Freshdesk - **Automated Ticket Management**: Handle ticket creation, updates, and responses ## Components ### Tools The server offers several tools for Freshdesk operations: - `create_ticket`: Create new support tickets - **Inputs**: - `subject` (string, required): Ticket subject - `description` (string, required): Ticket description - `source` (number, required): Ticket source code - `priority` (number, required): Ticket priority level - `status` (number, required): Ticket status code - `email` (string, optional): Email of the requester - `requester_id` (number, optional): ID of the requester - `custom_fields` (object, optional): Custom fields to set on the ticket - `additional_fields` (object, optional…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.