Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"enchant": {
"url": "https://enchant.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"enchant": {
"type": "http",
"url": "https://enchant.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Help desk identifier and API access token.
The identifier is the first part of your help desk address: acme for acme.enchant.com. For the token, install the API app in your help desk Settings → Apps and copy its access token. The API is available on paid Enchant plans. The token is used only to call the API on your behalf and to derive a private account id.
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: the login page asks for your Help desk identifier and API access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
enchant_list_tickets | read | 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_get_ticket | read | 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_users | read | List users (agents) 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_list_customers | read | 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_get_customer | read | Get customer Get one customer by id, with the contacts (emails, phones, Twitter names). Enchant REST: GET /customers/{id}. |
enchant_get_attachment | read | 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_create_ticket | write | 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_update_ticket | write | 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}. |
enchant_add_ticket_labels | write | Add labels to ticket WRITE: add one or more labels to a ticket without changing its other labels. Enchant REST: PUT /tickets/{id}/labels/{label_ids}. |
enchant_remove_ticket_labels | write | Remove labels from ticket 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 | Reply to customer 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_add_note | write | Add internal note WRITE: add an internal note to a ticket (not sent to the customer). Enchant REST: POST /tickets/{id}/messages (type note). |
enchant_create_customer | write | Create customer WRITE: create a customer with optional contacts (email, twitter, phone). Enchant REST: POST /customers. |
enchant_update_customer | write | 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_add_customer_contact | write | Add customer contact WRITE: add one contact (email, twitter or phone) to a customer. Enchant REST: POST /customers/{id}/contacts. |
enchant_delete_customer_contact | write | Delete customer contact WRITE, DELETES DATA: remove one contact from a customer. Enchant REST: DELETE /customers/{id}/contacts/{contact_id}. |
enchant_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
enchant_request_feature | Request a missing feature Tell usefulapi that the user needs something the Enchant tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
enchant_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Enchant tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
enchant_cancel_subscription | Cancel the Pro subscription Cancel the caller's Enchant Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run enchant_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this Enchant server only. Subscribe with enchant_upgrade (it returns a Stripe Checkout link). Cancel any time with enchant_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running enchant_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Enchant. The server calls the Enchant API with your own Enchant access, so it sees only the data that your account can see.
The login page asks for your Help desk identifier and API access token. See Before you connect for where to find them.
No. 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: the login page asks for your Help desk identifier and API access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Enchant API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Enchant.
Yes, if you approve it. 10 of the 16 Enchant tools can create or change data. The other 6 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Enchant server only. Run enchant_usage_status to see how many calls you used.
Ask the AI to run enchant_upgrade: it returns a Stripe Checkout link. To cancel, run enchant_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with enchant_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.