freshdesk

Tools

19 tools: 12 read-only, 0 change data, 7 high risk (delete, pay, send or run code).

1 tool can send messages; they are listed first.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 4,592 tokens of tool definitions and a 310 ms handshake.

• high riskfreshdesk_reply_ticketsends messagesAdd a public reply to a ticket (sent to the requester). Freshdesk REST: POST /tickets/{id}/reply.
• high riskfreshdesk_create_ticketCreate a ticket. `subject` and `description` (HTML) are required, plus a requester - provide at least one of `email`, `requester_id`, or `phone`. status: 2=Open, 3=Pending, 4=Resolved, 5=Closed. priority: 1=Low, 2=Medium, 3=High, 4=Urgent. source: 1=Email, 2=Portal, 3=Phone, 7=Chat, 9=Feedbackwid...
• high riskfreshdesk_update_ticketUpdate fields on an existing ticket. Only provided fields are changed. status: 2=Open, 3=Pending, 4=Resolved, 5=Closed. priority: 1=Low, 2=Medium, 3=High, 4=Urgent. Freshdesk REST: PUT /tickets/{id}.
• high riskfreshdesk_add_noteAdd a note to a ticket. Notes are internal (private) by default; set `private: false` for a public note. Freshdesk REST: POST /tickets/{id}/notes.
• high riskfreshdesk_create_contactCreate a contact. `name` is required. Freshdesk REST: POST /contacts.
• high riskfreshdesk_update_contactUpdate fields on an existing contact. Only provided fields are changed. Freshdesk REST: PUT /contacts/{id}.
• high riskfreshdesk_create_companyCreate a company. `name` is required. Freshdesk REST: POST /companies.
• read-onlyfreshdesk_list_ticketsList/filter tickets (max page 300). Freshdesk REST: GET /tickets.
• read-onlyfreshdesk_get_ticketGet a single ticket by id. Freshdesk REST: GET /tickets/{id}.
• read-onlyfreshdesk_search_ticketsSearch tickets with the Freshdesk query DSL. The query VALUE is wrapped in double quotes automatically. Examples: `status:2 AND priority:3`, `created_at:>'2026-01-01'`, `agent_id:123`, `group_id:45`, `tag:'urgent'`. Freshdesk REST: GET /search/tickets.
• read-onlyfreshdesk_list_ticket_conversationsList the conversations (replies and notes) on a ticket. Freshdesk REST: GET /tickets/{id}/conversations.
• read-onlyfreshdesk_list_contactsList/filter contacts. Freshdesk REST: GET /contacts.
• read-onlyfreshdesk_get_contactGet a single contact by id. Freshdesk REST: GET /contacts/{id}.
• read-onlyfreshdesk_search_contactsSearch contacts with the Freshdesk query DSL. The query VALUE is wrapped in double quotes automatically. Examples: `name:'ada'`, `email:'ada@example.com'`, `company_id:123`. Freshdesk REST: GET /search/contacts.
• read-onlyfreshdesk_list_companiesList companies. Freshdesk REST: GET /companies.
• read-onlyfreshdesk_get_companyGet a single company by id. Freshdesk REST: GET /companies/{id}.
• read-onlyfreshdesk_list_agentsList/filter agents. Freshdesk REST: GET /agents.
• read-onlyfreshdesk_get_agentGet a single agent by id. Freshdesk REST: GET /agents/{id}.
• read-onlyfreshdesk_list_groupsList groups (agent groups tickets are routed to). Freshdesk REST: GET /groups.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-03, 310 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-042026-10-03

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in CRM and sales, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/freshdesk.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/freshdesk.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=freshdesk.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/freshdesk.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/freshdesk.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=freshdesk.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.