Deskpro MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.39.1Updated Nov 14, 2026

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

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableKnowledge & MemoryBusiness & Commerce

Overview

AI-generated overview

Hosted Deskpro helpdesk connector that lets an assistant search and read tickets, people, organizations and KB articles, and create tickets, replies and…

What you can do
  • Search the helpdesk and confirm the signed-in agent
  • List and read tickets, including full message threads, statuses, departments and agents
  • Look up people and organizations, with their ticket histories
  • Browse knowledgebase articles
  • Create tickets and organizations, update ticket fields, and add replies or internal notes
  • Check usage and manage the subscription plan
When to use it
Useful when support agents or teams want an assistant to triage open tickets, summarize conversations, look up a customer's history, draft replies, or file new tickets in Deskpro without switching tools.
Requirements
Remote MCP endpoint connected over OAuth; no local install. On first connect you supply your Deskpro helpdesk URL and an API key in id:code format, which the service validates and stores per user. A free plan allows 50 tool calls per month; paid plans raise the limit.
Before you install
Write tools change Deskpro data: creating tickets and organizations, updating ticket fields, and adding messages. A message sent with is_note=false is emailed to the requester and cannot be unsent. Creating a ticket may trigger requester emails. Your Deskpro URL and API key are stored by the third-party host. Paid plans are billed through Stripe, and plan changes charge the price difference immediately with no refund on cancellation.

Installation

In SourceWeft

  1. Open Deskpro MCP by usefulapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fdeskpro/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "deskpro-by-usefulapi": {
      "type": "http",
      "url": "https://deskpro.usefulapi.io/mcp"
    }
  }
}

README

Deskpro MCP by usefulapi

Use Deskpro from Claude, Cursor, or any MCP client — search tickets, people, organizations and knowledgebase articles, and create tickets and replies. Hosted, no local install: connect with your own Deskpro credentials.

Live endpoint: https://deskpro.usefulapi.io/mcp · Homepage: https://usefulapi.io/deskpro

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://deskpro.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http deskpro https://deskpro.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "deskpro": {      "url": "https://deskpro.usefulapi.io/mcp"    }  }}

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Deskpro credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/deskpro/

On first connect you'll provide your Deskpro helpdesk URL (subdomain or full https address) and an API key (Admin → Apps & Integrations → API Keys, id:code format). They're validated, stored per-user, and scoped to you — no keys in config files.

Tools

ToolTypeWhat it does
deskpro_get_mereadGet the authenticated agent
deskpro_list_ticketsreadList tickets
deskpro_get_ticketreadGet one ticket
deskpro_list_ticket_messagesreadList a ticket's messages
deskpro_list_peoplereadList people
deskpro_get_personreadGet one person
deskpro_list_person_ticketsreadList a person's tickets
deskpro_list_organizationsreadList organizations
deskpro_get_organizationreadGet one organization
deskpro_list_organization_ticketsreadList an organization's tickets
deskpro_list_articlesreadList knowledgebase articles
deskpro_get_articlereadGet one article
deskpro_list_departmentsreadList ticket departments
deskpro_list_agentsreadList agents
deskpro_list_ticket_statusesreadList ticket statuses
deskpro_searchreadSearch the helpdesk
deskpro_create_ticketwriteCreate a ticket
deskpro_update_ticketwriteUpdate a ticket
deskpro_add_ticket_messagewriteReply to a ticket or add a note
deskpro_create_organizationwriteCreate an organization
deskpro_usage_statusmetaUsage status (free-tier meter)
deskpro_request_featuremetaRequest a missing feature
deskpro_upgrademetaUpgrade to Pro or Pro+
deskpro_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro (per user)$9/mo or $90/yr (2 months free)10,000 tool calls / month
Pro+ (per user)$39/mo or $390/yr (2 months free)100,000 tool calls / month

Each paid plan covers this server only. Ask your AI to run deskpro_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with deskpro_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with deskpro_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT © usefulapi. Not affiliated with or endorsed by Deskpro.

Source: servers/deskpro/README.md at commit f22f848

Tools

20

deskpro_get_me

Get the authenticated agent

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.

Takes no parameters.

deskpro_list_tickets

List tickets

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.

Parametersidspageagentcountlabelspersonstatusincludeorder_bydepartmentgroup_sortorganization

deskpro_get_ticket

Get one ticket

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}.

Parametersincludeticket_idrequired

deskpro_list_ticket_messages

List a ticket's messages

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.

Parameterspagecountincludeticket_idrequired

deskpro_list_people

List people

List people (end users and agents), searchable by name and filterable by email, organization or agent flag. Deskpro: GET /api/v2/people.

Parameterspagecountsearchincludeis_agentorder_byorder_dirorganizationprimary_email

deskpro_get_person

Get one person

Fetch a single person by id — name, emails, phone numbers, organization, labels, custom fields and ticket count. Deskpro: GET /api/v2/people/{id}.

Parametersincludeperson_idrequired

deskpro_list_person_tickets

List a person's tickets

List the tickets raised by one person — their support history. Deskpro: GET /api/v2/people/{id}/tickets.

Parameterspagecountperson_idrequired

deskpro_list_organizations

List organizations

List customer organizations, filterable by name or labels. Deskpro: GET /api/v2/organizations.

Parametersnamepagecountlabelssearchinclude

deskpro_get_organization

Get one organization

Fetch a single organization by id — name, summary, email domains, labels, custom fields and ticket count. Deskpro: GET /api/v2/organizations/{id}.

Parametersincludeorganization_idrequired

deskpro_list_organization_tickets

List an organization's tickets

List the tickets belonging to one organization. Deskpro: GET /api/v2/organizations/{id}/tickets.

Parameterspagecountorganization_idrequired

deskpro_list_articles

List knowledgebase articles

List knowledgebase articles, filterable by category, status and author. Deskpro: GET /api/v2/articles.

Parameterspagecountauthorstatuscategoryorder_by

deskpro_get_article

Get one article

Fetch a single knowledgebase article by id — title, content, status, categories and labels. Deskpro: GET /api/v2/articles/{id}.

Parametersarticle_idrequired

deskpro_list_departments

List ticket departments

List the ticket departments (id, title, parent, whether tickets/chat are enabled) — needed to route a new ticket. Deskpro: GET /api/v2/ticket_departments.

Parameterspagecount

deskpro_list_agents

List agents

List the helpdesk's agents (id, name, email, online state) — needed to assign a ticket. Deskpro: GET /api/v2/agents.

Parameterspagecountonline

deskpro_list_ticket_statuses

List ticket statuses

List the ticket statuses and custom sub-statuses (status_type, status_code, title) configured on the helpdesk. Deskpro: GET /api/v2/ticket_statuses.

Parameterspagecountstatus_type

deskpro_create_ticket

Create a ticket

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.

Parameterslabelsstatusmessagerequiredsubjectrequiredurgencyagent_idperson_idagent_teamdepartmentperson_nameorganizationperson_email+1 more

deskpro_update_ticket

Update a ticket

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}.

Parameterslabelsstatusis_holdsubjecturgencyagent_idticket_idrequiredagent_teamdepartmentorganization

deskpro_add_ticket_message

Reply to a ticket or add a note

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.

Parametersformatis_noterequiredmessagerequiredticket_idrequired

deskpro_create_organization

Create an organization

Create a customer organization. Email domains auto-associate people with matching addresses. Deskpro: POST /api/v2/organizations.

Parametersnamerequiredlabelssummaryemail_domains

Version history

25
  1. v1.39.1LatestNov 13, 2026
  2. v1.38.0Nov 12, 2026
  3. v1.37.3Nov 11, 2026
  4. v1.36.5Nov 8, 2026
  5. v1.36.4Nov 7, 2026
  6. v1.35.3Nov 5, 2026
  7. v1.35.2Nov 5, 2026
  8. v1.35.1Nov 4, 2026
  9. v1.35.0Nov 3, 2026
  10. v1.34.1Nov 3, 2026
  11. v1.33.0Nov 1, 2026
  12. v1.31.0Oct 31, 2026
  13. v1.30.0Oct 31, 2026
  14. v1.29.2Oct 30, 2026
  15. v1.29.0Oct 30, 2026
  16. v1.24.0Oct 26, 2026
  17. v1.21.3Oct 25, 2026
  18. v1.21.0Oct 25, 2026
  19. v1.20.0Oct 24, 2026
  20. v1.17.0Oct 23, 2026
  21. v1.16.4Oct 22, 2026
  22. v1.16.3Oct 21, 2026
  23. v1.11.1Oct 9, 2026
  24. v1.10.0Oct 9, 2026
  25. v1.0.0Sep 30, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations