Octadesk MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.0.1Updated Nov 7, 2026

Search tickets, read conversations and people; create and update tickets and people in Octadesk.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Hosted MCP connector for Octadesk helpdesk: search and read tickets, conversations and people, and create or update tickets and people.

What you can do
  • Search and read tickets, including saved custom lists and all tickets of one requester
  • Read a ticket's conversation: replies, internal notes and property changes in order
  • Find people by e-mail or id, and search requesters and agents by e-mail or name
  • Create and update tickets, including status, priority, assignee, group, tags and public or internal comments
  • Create and update people records
  • Check monthly usage, request a missing feature, and manage a paid subscription
When to use it
Useful when you work in Octadesk support and want an assistant to triage tickets, summarize a ticket's history, look up a customer's tickets, or draft and file ticket updates without switching to the web app.
Requirements
Remote endpoint reached over streamable HTTP; no local install. Sign-in is by OAuth, and the login page asks for your Octadesk subdomain, a Legacy API token from Settings, and the account e-mail that owns the token; the server stores them per user. No keys go in the client config.
Before you install
Write tools create and update tickets and people, and a public comment on a ticket is e-mailed to the requester, so confirm before running them. The service is metered: free plan 50 calls a month, paid plans billed through a Stripe checkout link, with no refund for the current period on cancellation. Your Octadesk credentials and token are stored by the third-party host.

Installation

In SourceWeft

  1. Open Octadesk 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%2Foctadesk/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": {
    "octadesk-by-usefulapi": {
      "type": "http",
      "url": "https://octadesk.usefulapi.io/mcp"
    }
  }
}

README

Octadesk MCP by usefulapi

Use your Octadesk account from Claude, Cursor, or any MCP client. It searches tickets and people, reads ticket conversations, and creates and updates tickets and people. Hosted, no local install: connect with your own credentials.

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

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://octadesk.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http octadesk https://octadesk.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": {    "octadesk": {      "url": "https://octadesk.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 Octadesk credentials.

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

On first connect you provide your Octadesk subdomain (the acme part of acme.octadesk.com), your Legacy API token from Settings → API → Token API Octadesk (Legacy), and the account e-mail of the account that owns the token. The server validates them and stores them per user. No keys go in config files.

Tools

ToolTypeWhat it does
octadesk_search_ticketsreadSearch tickets
octadesk_get_ticketreadGet ticket
octadesk_get_ticket_interactionsreadGet ticket conversation
octadesk_list_requester_ticketsreadList tickets of a requester
octadesk_list_custom_ticket_listsreadList custom ticket lists
octadesk_find_person_by_emailreadFind person by e-mail
octadesk_get_personreadGet person
octadesk_search_requestersreadSearch requesters
octadesk_search_agentsreadSearch agents
octadesk_create_ticketwriteCreate ticket
octadesk_update_ticketwriteUpdate ticket
octadesk_create_personwriteCreate person
octadesk_update_personwriteUpdate person
octadesk_usage_statusmetaUsage status (free-tier meter)
octadesk_request_featuremetaRequest a missing feature
octadesk_upgrademetaUpgrade to Pro or Pro+
octadesk_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)Unlimited*

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with octadesk_upgrade (it returns a Stripe Checkout link). Cancel any time with octadesk_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running octadesk_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT — see LICENSE. Documentation only; the server is hosted.

Source: servers/octadesk/README.md at commit 2450437

Tools

13

octadesk_search_tickets

Search tickets

Search tickets with optional filters. Returns the page of tickets plus paging fields (total_count, search_id, next_page_url). For the next page, pass the same filters with the returned search_id and page + 1. GET /tickets/search.

Parameterspagetagstaketypenumberstatuscontentsort_bygroup_idprioritysearch_idassignee_id+3 more

octadesk_get_ticket

Get ticket

Get one ticket by its number, with its fields and status. GET /tickets/{number}.

Parametersnumberrequired

octadesk_get_ticket_interactions

Get ticket conversation

List the interactions of one ticket: replies, internal notes and property changes, in order. GET /tickets/{number}/interactions.

Parametersnumberrequired

octadesk_list_requester_tickets

List tickets of a requester

List the tickets of one requester. Pass last_number to read past the last ticket of the previous page. GET /tickets.

Parameterslast_numberrequester_idrequired

octadesk_list_custom_ticket_lists

List custom ticket lists

List the saved custom ticket lists (views) of the account. GET /tickets/custom-lists.

Takes no parameters.

octadesk_find_person_by_email

Find person by e-mail

Find one person (requester or agent) by exact e-mail address. GET /persons?email=.

Parametersemailrequired

octadesk_get_person

Get person

Get one person by id. GET /persons/{id}.

Parametersidrequired

octadesk_search_requesters

Search requesters

Search requesters (customers who open tickets) by e-mail or name. GET /persons/requesters.

Parameterspagekeywordrequireddetailed

octadesk_search_agents

Search agents

Search agents (staff who work tickets) by e-mail or name. GET /persons/agents.

Parameterspagekeywordrequireddetailed

octadesk_create_ticket

Create ticket

Create a ticket. Common keys of `ticket`: summary, requester ({ email, name } or { id }), idGroupAssigned, idAssigned, idPriority, idCurrentStatus, idSubject, tags (string array), comments ({ internal: { content } } for an agent-only note, { public: { content } } for a reply the requester can read). POST /tickets.

Parametersticketrequired

octadesk_update_ticket

Update ticket

Change fields of one ticket, for example status, priority, assignee or group. Send only the fields to change. A `comments.public` entry is e-mailed to the requester. PUT /tickets/{number}.

Parametersfieldsrequirednumberrequired

octadesk_create_person

Create person

Create a person (requester or agent). Send the person fields, for example email and name. POST /persons.

Parameterspersonrequired

octadesk_update_person

Update person

Change fields of one person. Send only the fields to change. PATCH /persons/{id}.

Parametersidrequiredfieldsrequired

Version history

1
  1. v1.0.1LatestNov 7, 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