# Desk365 MCP by usefulapi

> Desk365 MCP by usefulapi is an MCP server. Read Desk365 tickets, conversations, contacts, companies, time entries and knowledge articles. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Website:** https://usefulapi.io/desk365/
- **Repository:** https://github.com/m190/usefulapi-mcp/tree/HEAD/servers/desk365
- **MCP Registry name:** io.usefulapi/desk365
- **Listing updated:** 2026-11-13

## About

Read Desk365 tickets, conversations, contacts, companies, time entries and knowledge articles.

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http desk365 https://desk365.usefulapi.io/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://desk365.usefulapi.io/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "desk365": {
      "url": "https://desk365.usefulapi.io/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "desk365": {
      "type": "http",
      "url": "https://desk365.usefulapi.io/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "desk365": {
      "serverUrl": "https://desk365.usefulapi.io/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "desk365": {
      "type": "http",
      "url": "https://desk365.usefulapi.io/mcp"
    }
  }
}
```

## Tools

- `desk365_add_ticket_reply`: WRITE: preview a public agent reply, optionally appending signature_html. With confirm:true and the approved preview_hash, SENDS AN EMAIL to the ticket contact and explicit CC/BCC recipients. Supply an explicit sender and agent. Reuse operation_id for status/retries; uncertain attempts are never replayed. Confirmed sends require hosted persistent operation storage.
- `desk365_reply_operation_status`: Read the stored state and reply ID of a previous send operation. Does not send or retry any email. If uncertain, reconcile the original attempt in Desk365; do not create a new operation ID to blindly retry it.
- `desk365_set_ticket_status`: WRITE: change only a ticket's status by its ticket number, including closing or resolving it. Supply the exact status name configured in the helpdesk (for example Resolved or Closed); no priority, assignee or other fields are changed. Desk365 may run status automations and send notifications. Pass confirm=true after the user approved the ticket and destination status. PUT /v3/tickets/update?ticket
- `desk365_list_tickets`: List helpdesk tickets, newest first by default, with subject, status, priority (1 Low, 5 Medium, 10 High, 20 Urgent), source, assignee, group, category, contact, company, SLA and dates. Filter by status, priority, type, group, assignee, category, contact, company or source. Use "--" in a list to match unassigned/empty. Descriptions are left out unless include_description is set. GET /v3/tickets.
- `desk365_search_tickets`: Full-text search over tickets, most relevant first. Searches subject and ticket number by default; widen it with search_in (description, replies and notes, attachment names, custom fields, contacts and companies, archived tickets). Double quotes around a phrase match it exactly; *text* matches inside words. GET /v3/tickets/search.
- `desk365_get_ticket`: Everything on one ticket by its number: subject, description, status, priority, source, assignee, group, category, contact, company, SLA, due date, response/resolution durations (minutes), custom fields, watchers. GET /v3/tickets/details.
- `desk365_get_ticket_conversations`: The conversation on a ticket: customer replies, agent replies, private and public notes and forwarded messages, each with sender, recipients, HTML and plain-text body, attachment details and time. The original description is not included (it is on desk365_get_ticket). GET /v3/tickets/conversations.
- `desk365_list_contacts`: List contacts (customers/requesters), 30 per call, sorted by name by default, optionally only those of one company. GET /v3/contacts.
- `desk365_get_contact`: One contact by primary email (or, if the primary is not known, a secondary email): name, title, phones, company, departments, custom fields. GET /v3/contacts/details.
- `desk365_list_companies`: List companies (customer organisations), 30 per call, sorted by name. GET /v3/companies.
- `desk365_get_company`: One company by exact name: description, phone, address, SLA, domains, departments, custom fields. GET /v3/companies/details.
- `desk365_list_time_entries`: List logged time entries (ticket, agent, minutes, billable, note), filtered by ticket, agent, company, billable flag, running timers or date ranges. GET /v3/time_entries.
- `desk365_get_time_entry`: One time entry by id. GET /v3/time_entries/details.
- `desk365_list_survey_ratings`: Customer satisfaction survey ratings (type 1 CSAT, 2 five-star, 3 NPS), oldest reply first, 30 per call. GET /v3/surveys/ratings.
- `desk365_list_kb_articles`: The titles of all live knowledge base articles. Open one with desk365_get_kb_article. GET /v3/kb/article/.
- `desk365_get_kb_article`: A live knowledge base article by its exact title: HTML and plain-text content, category, folder, author, views, likes and status (0 unpublished, 1 published). GET /v3/kb/article/details.

## FAQ

### How do I add Desk365 MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http desk365 https://desk365.usefulapi.io/mcp

---
Source: https://ai-powered.com/mcp/desk365-mcp-by-usefulapi
