deskpro

Tools

20 tools: 16 read-only, 0 change data, 4 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,974 tokens of tool definitions and a 314 ms handshake.

• high riskdeskpro_add_ticket_messagesends messagesAdd a message to a ticket as the key's agent. With is_note=true it is an internal agent note (not shown to the requester); with is_note=false it is a REPLY that the helpdesk emails to the requester - that cannot be unsent. Deskpro: POST /api/v2/tickets/{id}/messages.
• high riskdeskpro_create_ticketOpen a new ticket for a requester (by person id, or by email - Deskpro creates the person if the email is new) with a first message. Depending on the helpdesk's triggers this may email the requester. Returns the created ticket. Deskpro: POST /api/v2/tickets.
• high riskdeskpro_update_ticketChange a ticket's subject, status, assignment, department, organization, urgency, hold state or labels. Only the fields you pass are sent. Reversible by updating again. Cannot set the hidden (deleted/spam) status. Deskpro: PUT /api/v2/tickets/{id}.
• high riskdeskpro_create_organizationCreate a customer organization. Email domains auto-associate people with matching addresses. Deskpro: POST /api/v2/organizations.
• read-onlydeskpro_get_meReturn who the API key acts as - the auth method, the bound person id and their profile. A cheap way to confirm the helpdesk URL and key are right. Deskpro: GET /api/v2/me.
• read-onlydeskpro_list_ticketsList tickets, filtered by status, assigned agent, requester, organization, department or labels, and sorted. Returns ticket objects (id, ref, subject, ticket_status, agent, person, department, urgency, labels, dates) plus pagination meta. Deskpro: GET /api/v2/tickets.
• read-onlydeskpro_get_ticketFetch a single ticket by id, with its subject, status, assignment, requester, labels, custom fields, SLA state and timing. A merged ticket redirects to the ticket it was merged into. Deskpro: GET /api/v2/tickets/{id}.
• read-onlydeskpro_list_ticket_messagesList the conversation on one ticket - every reply and agent note, with its author, date, is_agent_note flag and HTML body. Deskpro: GET /api/v2/tickets/{id}/messages.
• read-onlydeskpro_list_peopleList people (end users and agents), searchable by name and filterable by email, organization or agent flag. Deskpro: GET /api/v2/people.
• read-onlydeskpro_get_personFetch a single person by id - name, emails, phone numbers, organization, labels, custom fields and ticket count. Deskpro: GET /api/v2/people/{id}.
• read-onlydeskpro_list_person_ticketsList the tickets raised by one person - their support history. Deskpro: GET /api/v2/people/{id}/tickets.
• read-onlydeskpro_list_organizationsList customer organizations, filterable by name or labels. Deskpro: GET /api/v2/organizations.
• read-onlydeskpro_get_organizationFetch a single organization by id - name, summary, email domains, labels, custom fields and ticket count. Deskpro: GET /api/v2/organizations/{id}.
• read-onlydeskpro_list_organization_ticketsList the tickets belonging to one organization. Deskpro: GET /api/v2/organizations/{id}/tickets.
• read-onlydeskpro_list_articlesList knowledgebase articles, filterable by category, status and author. Deskpro: GET /api/v2/articles.
• read-onlydeskpro_get_articleFetch a single knowledgebase article by id - title, content, status, categories and labels. Deskpro: GET /api/v2/articles/{id}.
• read-onlydeskpro_list_departmentsList the ticket departments (id, title, parent, whether tickets/chat are enabled) - needed to route a new ticket. Deskpro: GET /api/v2/ticket_departments.
• read-onlydeskpro_list_agentsList the helpdesk's agents (id, name, email, online state) - needed to assign a ticket. Deskpro: GET /api/v2/agents.
• read-onlydeskpro_list_ticket_statusesList the ticket statuses and custom sub-statuses (status_type, status_code, title) configured on the helpdesk. Deskpro: GET /api/v2/ticket_statuses.
• read-onlydeskpro_searchQuick search across tickets, people, organizations, articles, news, downloads, community topics and chats; results are grouped by type. Deskpro: GET /api/v2/search.

Levels are read from each tool's name, description and annotations. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-03, 314 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 Marketing, email and messaging, 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/deskpro.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/deskpro.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).

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/deskpro.usefulapi.io/mcp.js" async></script>

Or an iframe:

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

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.