Freshdesk MCP vs Simple Support System MCP
A side-by-side look at the Freshdesk MCP and Simple Support System MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Freshdesk MCP for support & service management work over a hosted endpoint; choose Simple Support System MCP for support & service management. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Freshdesk MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
get_ticket, get_ticket_summary, batch_get_ticket_summaries.
Choose Simple Support System MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- You have the keys it needs:
SIMPLE_SUPPORT_SYSTEM_BASE_URL, SIMPLE_SUPPORT_SYSTEM_API_KEY, SIMPLE_SUPPORT_SYSTEM_API_PATH, SIMPLE_SUPPORT_SYSTEM_PROJECT_TOKEN, SIMPLE_SUPPORT_SYSTEM_TIMEOUT_MS. - You want tools like
list_tickets, get_ticket, reply_to_ticket.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 51/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | SIMPLE_SUPPORT_SYSTEM_BASE_URLSIMPLE_SUPPORT_SYSTEM_API_KEYSIMPLE_SUPPORT_SYSTEM_API_PATHSIMPLE_SUPPORT_SYSTEM_PROJECT_TOKENSIMPLE_SUPPORT_SYSTEM_TIMEOUT_MS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 15 | 23 |
| Full listing | View Freshdesk MCP | View Simple Support System MCP |
Tools & capabilities
Freshdesk MCP tools 15
get_ticketFetch a single ticket by ID. Returns status name, group name, company ID.get_ticket_summaryTicket + all conversations + attachments in one call.batch_get_ticket_summariesMultiple ticket summaries in parallel.search_ticketsFilter by query, status, priority, type, overdue, escalated, dates, company, requester, agent, group. Full ticket history.list_ticketsAll tickets with optional filters.get_conversationsAll replies and notes for a ticket (fully paginated).list_attachmentsAll attachments across ticket and conversations. Filters scanning placeholders.get_attachment_textExtract text from docx, xlsx, json, txt, csv, png, jpg (Vision OCR).query_attachmentSearch within a JSON attachment.find_image_attachmentsScan multiple tickets for image attachments.get_description_imagesOCR inline images in ticket description HTML and conversation replies.find_requesterSearch contacts by name/email → requester_id.- +3 more on the listing page
Simple Support System MCP tools 23
list_ticketsLists tickets with filters for project, state, type, priority, assignee, text search and change date, sorted and paged. Compact summaries by default.get_ticketReads one ticket with its attachments and, unless switched off, all of its comments.reply_to_ticketPosts a reply as a comment on a ticket and triggers the notification mails.set_ticket_stateMoves a ticket to another workflow state and notifies everyone involved.create_ticketCreates a ticket in a project, by project id or project handle, optionally with uploaded files.update_ticketChanges title, content, type, priority or assignee. Only the given fields are touched.approve_ticketApproves a moderated ticket.delete_ticketDeletes a ticket with all comments and attachment links. Irreversible, needs `confirm: true`.list_ticket_commentsLists the comments of a ticket.update_commentReplaces the text of a comment.approve_commentApproves a moderated comment.delete_commentDeletes a comment. Irreversible, needs `confirm: true`.- +11 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Freshdesk MCP
{
"mcpServers": {
"omnom62-freshdesk-mcp": {
"url": "https://your-deployment-url/mcp"
}
}
}
Simple Support System MCP
No confirmed install command for Simple Support System MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Freshdesk MCP is categorized under Support & Service Management and uses a remote HTTP/SSE transport. Simple Support System MCP belongs to Support & Service Management and uses an install path we have not confirmed yet. Pick Freshdesk MCP for support & service management work and Simple Support System MCP for support & service management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Simple Support System MCP has no confirmed install command yet — follow its own setup instructions.
Freshdesk MCP has no declared pricing — check the project's own site. Simple Support System MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add omnom62-freshdesk-mcp and simple-support-system-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Freshdesk MCP has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Simple Support System MCP has 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.