Enchant MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Enchant MCP by usefulapi is answering right now. Last checked 8 min ago. It exposes 16 tools. Last commit 10 Oct 2026.

Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers.

Uptime history 28 hours of history

28 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

126 ms

Response time

average over 24h

Stars

last commit 10 Oct 2026

Nothing serious here today

Today is the operative word: we check Enchant MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "enchant": {
      "url": "https://enchant.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.enchant]
url = "https://enchant.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "enchant": {
      "url": "https://enchant.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "enchant": {
      "url": "https://enchant.usefulapi.io/mcp"
    }
  }
}

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

enchant

enchant_add_customer_contact

WRITE: add one contact (email, twitter or phone) to a customer. Enchant REST: POST /customers/{id}/contacts.

enchant_add_note

WRITE: add an internal note to a ticket (not sent to the customer). Enchant REST: POST /tickets/{id}/messages (type note).

enchant_add_ticket_labels

WRITE: add one or more labels to a ticket without changing its other labels. Enchant REST: PUT /tickets/{id}/labels/{label_ids}.

enchant_create_customer

WRITE: create a customer with optional contacts (email, twitter, phone). Enchant REST: POST /customers.

enchant_create_ticket

WRITE: create an email ticket. Give customer_id, or a customer (matched by contact email, created if new). Optionally add the customer's first message with body (needs the customer's email). Enchant REST: POST /tickets.

enchant_delete_customer_contact

WRITE, DELETES DATA: remove one contact from a customer. Enchant REST: DELETE /customers/{id}/contacts/{contact_id}.

enchant_get_attachment

Get the metadata of an attachment (name, size, MIME type) by id; attachment ids appear in ticket messages. Enchant REST: GET /attachments/{id}.

enchant_get_customer

Get one customer by id, with the contacts (emails, phones, Twitter names). Enchant REST: GET /customers/{id}.

enchant_get_ticket

Get one ticket by id. Embed related data with `embed`: messages (the conversation: replies and notes), customer, user, inbox, labels. Each embedded type costs 1 extra rate-limit credit. Enchant REST: GET /tickets/{id}.

enchant_list_customers

List customers, or find one by contact: set contact_type and contact_value (for example email + an address). Enchant REST: GET /customers.

enchant_list_tickets

List and filter tickets (newest first by default). Enchant REST: GET /tickets. Use user_ids ["null"] for unassigned tickets. Each result has a short summary; use enchant_get_ticket for messages.

enchant_list_users

List the help desk users (agents): id, name, email. Use the ids to assign tickets and to author replies and notes. Enchant REST: GET /users.

enchant_remove_ticket_labels

WRITE: remove one or more labels from a ticket; its other labels stay. Enchant REST: DELETE /tickets/{id}/labels/{label_ids}.

enchant_reply_to_ticket

WRITE: send an outbound reply on a ticket. This SENDS A REAL EMAIL to the customer address in `to`. Use enchant_add_note for an internal note. Enchant REST: POST /tickets/{id}/messages (type reply, direction out).

enchant_update_customer

WRITE: update a customer's name or summary. If `contacts` is given, it REPLACES the contact list; use enchant_add_customer_contact to add one. Enchant REST: PATCH /customers/{id}.

enchant_update_ticket

WRITE: change a ticket: state (open, hold, closed), assignee, inbox, subject, spam or trash (not both true). label_ids REPLACES all labels (empty array clears them); use enchant_add_ticket_labels to keep existing ones. Enchant REST: PATCH /tickets/{id}.

Endpoints

URL	Transport	State	Latency	Checked
https://enchant.usefulapi.io/mcp	streamable-http	answering	80 ms	8 min ago

Alternatives to Enchant MCP by usefulapi

same job, measured the same way

eDesk MCP by usefulapi

by usefulapi

Work with eDesk support tickets, replies, internal notes, contacts and sales orders.

18 tools answering

HelpCrunch MCP by usefulapi

by usefulapi

Manage HelpCrunch chats, customers, agents and knowledge-base articles.

12 tools answering

Veeqo MCP by usefulapi

by usefulapi

Read Veeqo orders, products, stock, warehouses, customers and POs; add notes, tag, set stock.

22 tools answering

SupportBee MCP by usefulapi

by usefulapi

Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive tickets.

22 tools answering

MCP Tomticket

by glira

TomTicket helpdesk MCP: tickets, replies, time, customers, chats, and KB

21 installs/wk local only

HappyFox MCP by usefulapi

by usefulapi

Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.

23 tools answering

Checkfront MCP by usefulapi

by usefulapi

Check Checkfront availability and rates, and manage booking sessions, bookings, customers and notes.

20 tools answering

Kayako MCP by usefulapi

by usefulapi

Search Kayako cases, replies, customers and help-center articles, and reply to or create cases.

21 tools answering

Enchant MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Enchant MCP by usefulapi do?

It exposes 16 tools, read directly from the server on our last check. Among them: enchant_add_customer_contact, enchant_add_note, enchant_add_ticket_labels, enchant_create_customer, enchant_create_ticket, enchant_delete_customer_contact and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Enchant MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 126 ms. The bar chart above shows every period we have measured.

How do I connect Enchant MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Enchant MCP by usefulapi need an API key?

No. Enchant MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Enchant MCP by usefulapi?

It answers our handshake in 126 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Enchant MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.