Skip to content

Deskpro MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.

Deletes · 4
CompareRegistry entry

20 tools: 4 can delete or cancel things and 16 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http deskpro https://deskpro.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

20 tools

Deletes or cancels 4Claude Code: deny
  • deskpro_add_ticket_messageAdd a message to a ticket as the key's agent.No findings

    Why it is in this group

    • The name "deskpro_add_ticket_message" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Add 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.

    Annotations the server declares

    • title: Reply to a ticket or add a note
    • destructiveHint: true
  • deskpro_create_organizationCreate a customer organization.No findings

    Why it is in this group

    • The name "deskpro_create_organization" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a customer organization. Email domains auto-associate people with matching addresses. Deskpro: POST /api/v2/organizations.

    Annotations the server declares

    • title: Create an organization
    • destructiveHint: true
  • deskpro_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.No findings

    Why it is in this group

    • The name "deskpro_create_ticket" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Open 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.

    Annotations the server declares

    • title: Create a ticket
    • destructiveHint: true
  • deskpro_update_ticketChange a ticket's subject, status, assignment, department, organization, urgency, hold state or labels.No findings

    Why it is in this group

    • The name "deskpro_update_ticket" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Change 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}.

    Annotations the server declares

    • title: Update a ticket
    • destructiveHint: true
Only reads 16Claude Code: allow
  • deskpro_get_articleFetch a single knowledgebase article by id — title, content, status, categories and labels.No findings

    Why it is in this group

    • The name "deskpro_get_article" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single knowledgebase article by id — title, content, status, categories and labels. Deskpro: GET /api/v2/articles/{id}.

    Annotations the server declares

    • title: Get one article
    • readOnlyHint: true
  • deskpro_get_meReturn who the API key acts as — the auth method, the bound person id and their profile.No findings

    Why it is in this group

    • The name "deskpro_get_me" says "get": a word for reading.
    Description, as the server wrote it
    Return 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.

    Annotations the server declares

    • title: Get the authenticated agent
    • readOnlyHint: true
  • deskpro_get_organizationFetch a single organization by id — name, summary, email domains, labels, custom fields and ticket count.No findings

    Why it is in this group

    • The name "deskpro_get_organization" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single organization by id — name, summary, email domains, labels, custom fields and ticket count. Deskpro: GET /api/v2/organizations/{id}.

    Annotations the server declares

    • title: Get one organization
    • readOnlyHint: true
  • deskpro_get_personFetch a single person by id — name, emails, phone numbers, organization, labels, custom fields and ticket count.No findings

    Why it is in this group

    • The name "deskpro_get_person" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single person by id — name, emails, phone numbers, organization, labels, custom fields and ticket count. Deskpro: GET /api/v2/people/{id}.

    Annotations the server declares

    • title: Get one person
    • readOnlyHint: true
  • deskpro_get_ticketFetch a single ticket by id, with its subject, status, assignment, requester, labels, custom fields, SLA state and timing.No findings

    Why it is in this group

    • The name "deskpro_get_ticket" says "get": a word for reading.
    Description, as the server wrote it
    Fetch 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}.

    Annotations the server declares

    • title: Get one ticket
    • readOnlyHint: true
  • deskpro_list_agentsList the helpdesk's agents (id, name, email, online state) — needed to assign a ticket.No findings

    Why it is in this group

    • The name "deskpro_list_agents" says "list": a word for reading.
    Description, as the server wrote it
    List the helpdesk's agents (id, name, email, online state) — needed to assign a ticket. Deskpro: GET /api/v2/agents.

    Annotations the server declares

    • title: List agents
    • readOnlyHint: true
  • deskpro_list_articlesList knowledgebase articles, filterable by category, status and author.No findings

    Why it is in this group

    • The name "deskpro_list_articles" says "list": a word for reading.
    Description, as the server wrote it
    List knowledgebase articles, filterable by category, status and author. Deskpro: GET /api/v2/articles.

    Annotations the server declares

    • title: List knowledgebase articles
    • readOnlyHint: true
  • deskpro_list_departmentsList the ticket departments (id, title, parent, whether tickets/chat are enabled) — needed to route a new ticket.No findings

    Why it is in this group

    • The name "deskpro_list_departments" says "list": a word for reading.
    Description, as the server wrote it
    List the ticket departments (id, title, parent, whether tickets/chat are enabled) — needed to route a new ticket. Deskpro: GET /api/v2/ticket_departments.

    Annotations the server declares

    • title: List ticket departments
    • readOnlyHint: true
  • deskpro_list_organization_ticketsList the tickets belonging to one organization.No findings

    Why it is in this group

    • The name "deskpro_list_organization_tickets" says "list": a word for reading.
    Description, as the server wrote it
    List the tickets belonging to one organization. Deskpro: GET /api/v2/organizations/{id}/tickets.

    Annotations the server declares

    • title: List an organization's tickets
    • readOnlyHint: true
  • deskpro_list_organizationsList customer organizations, filterable by name or labels.No findings

    Why it is in this group

    • The name "deskpro_list_organizations" says "list": a word for reading.
    Description, as the server wrote it
    List customer organizations, filterable by name or labels. Deskpro: GET /api/v2/organizations.

    Annotations the server declares

    • title: List organizations
    • readOnlyHint: true
  • deskpro_list_peopleList people (end users and agents), searchable by name and filterable by email, organization or agent flag.No findings

    Why it is in this group

    • The name "deskpro_list_people" says "list": a word for reading.
    Description, as the server wrote it
    List people (end users and agents), searchable by name and filterable by email, organization or agent flag. Deskpro: GET /api/v2/people.

    Annotations the server declares

    • title: List people
    • readOnlyHint: true
  • deskpro_list_person_ticketsList the tickets raised by one person — their support history.No findings

    Why it is in this group

    • The name "deskpro_list_person_tickets" says "list": a word for reading.
    Description, as the server wrote it
    List the tickets raised by one person — their support history. Deskpro: GET /api/v2/people/{id}/tickets.

    Annotations the server declares

    • title: List a person's tickets
    • readOnlyHint: true
  • deskpro_list_ticket_messagesList the conversation on one ticket — every reply and agent note, with its author, date, is_agent_note flag and HTML body.No findings

    Why it is in this group

    • The name "deskpro_list_ticket_messages" says "list": a word for reading.
    Description, as the server wrote it
    List 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.

    Annotations the server declares

    • title: List a ticket's messages
    • readOnlyHint: true
  • deskpro_list_ticket_statusesList the ticket statuses and custom sub-statuses (status_type, status_code, title) configured on the helpdesk.No findings

    Why it is in this group

    • The name "deskpro_list_ticket_statuses" says "list": a word for reading.
    Description, as the server wrote it
    List the ticket statuses and custom sub-statuses (status_type, status_code, title) configured on the helpdesk. Deskpro: GET /api/v2/ticket_statuses.

    Annotations the server declares

    • title: List ticket statuses
    • readOnlyHint: true
  • deskpro_list_ticketsList tickets, filtered by status, assigned agent, requester, organization, department or labels, and sorted.No findings

    Why it is in this group

    • The name "deskpro_list_tickets" says "list": a word for reading.
    Description, as the server wrote it
    List 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.

    Annotations the server declares

    • title: List tickets
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.16.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http deskpro https://deskpro.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__deskpro__deskpro_get_me",
      "mcp__deskpro__deskpro_list_tickets",
      "mcp__deskpro__deskpro_get_ticket",
      "mcp__deskpro__deskpro_list_ticket_messages",
      "mcp__deskpro__deskpro_list_people",
      "mcp__deskpro__deskpro_get_person",
      "mcp__deskpro__deskpro_list_person_tickets",
      "mcp__deskpro__deskpro_list_organizations",
      "mcp__deskpro__deskpro_get_organization",
      "mcp__deskpro__deskpro_list_organization_tickets",
      "mcp__deskpro__deskpro_list_articles",
      "mcp__deskpro__deskpro_get_article",
      "mcp__deskpro__deskpro_list_departments",
      "mcp__deskpro__deskpro_list_agents",
      "mcp__deskpro__deskpro_list_ticket_statuses",
      "mcp__deskpro__deskpro_search"
    ],
    "ask": [],
    "deny": [
      "mcp__deskpro__deskpro_create_ticket",
      "mcp__deskpro__deskpro_update_ticket",
      "mcp__deskpro__deskpro_add_ticket_message",
      "mcp__deskpro__deskpro_create_organization"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as deskpro. Review it before you use it.