Enchant MCP by usefulapi

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

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

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Hosted Enchant help desk server that lets an assistant list, read, reply to and manage support tickets, customers and agents.

What you can do
  • List and read tickets, with optional embedded messages, customer, assignee, inbox and labels
  • List agents and look up customers by id or by contact such as email
  • Create and update tickets, change state, assignee, inbox, subject, spam or trash, and add or remove labels
  • Send outbound replies to customers and add internal notes
  • Create and update customers and add or remove their contacts
  • Check usage, request a feature, upgrade or cancel a subscription
When to use it
Use it when you want an assistant to triage an Enchant help desk, summarize ticket conversations, draft and send customer replies, or keep customer records and labels up to date without switching apps.
Requirements
Remote MCP endpoint added by URL only; no local install. Sign-in is via OAuth, and the login page asks for your own Enchant credentials. Do not add an Authorization header or API key to the client config. A free plan allows 50 tool calls per month; paid plans raise the limit.
Before you install
Many tools write data: creating and updating tickets and customers, changing labels, and deleting customer contacts. enchant_reply_to_ticket sends a real email to the customer address given, so confirm before sending. enchant_update_ticket with label_ids replaces all labels, and enchant_update_customer with contacts replaces the whole contact list. Paid plans cost money and are billed through a Stripe checkout link; cancellation runs to the end of the paid period with no refund.

Installation

In SourceWeft

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

README

Enchant MCP by usefulapi

Use Enchant from Claude, Cursor, or any MCP client — tickets, replies, notes, labels and customers. Hosted, no local install: connect with your own Enchant credentials.

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

Connect

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

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

Tools

ToolTypeWhat it does
enchant_list_ticketsreadList tickets
enchant_get_ticketreadGet ticket
enchant_list_usersreadList users (agents)
enchant_list_customersreadList customers
enchant_get_customerreadGet customer
enchant_get_attachmentreadGet attachment
enchant_create_ticketwriteCreate ticket
enchant_update_ticketwriteUpdate ticket
enchant_add_ticket_labelswriteAdd labels to ticket
enchant_remove_ticket_labelswriteRemove labels from ticket
enchant_reply_to_ticketwriteReply to customer
enchant_add_notewriteAdd internal note
enchant_create_customerwriteCreate customer
enchant_update_customerwriteUpdate customer
enchant_add_customer_contactwriteAdd customer contact
enchant_delete_customer_contactwriteDelete customer contact
enchant_usage_statusmetaUsage status (free-tier meter)
enchant_request_featuremetaRequest a missing feature
enchant_upgrademetaUpgrade to Pro or Pro+
enchant_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 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].

License

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

Source: servers/enchant/README.md at commit 4046075

Tools

16

enchant_list_tickets

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.

Parametersidspagesortspamcounttrashtypesstatesper_pageuser_idsinbox_idslabel_ids+2 more

enchant_get_ticket

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

Parametersidrequiredembed

enchant_list_users

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.

Parameterspageper_page

enchant_list_customers

List customers

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

Parameterspagecountper_pagecontact_typecontact_valuesince_created_at

enchant_get_customer

Get customer

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

Parametersidrequired

enchant_get_attachment

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

Parametersidrequired

enchant_create_ticket

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.

Parametersbodysubjectrequireduser_idcustomerinbox_idcustomer_id

enchant_update_ticket

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

Parametersidrequiredspamstatetrashsubjectuser_idinbox_idlabel_ids

enchant_add_ticket_labels

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

Parametersidrequiredlabel_idsrequired

enchant_remove_ticket_labels

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

Parametersidrequiredlabel_idsrequired

enchant_reply_to_ticket

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

Parametersidrequiredtorequiredbodyrequiredhtmluser_idrequiredattachment_ids

enchant_add_note

Add internal note

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

Parametersidrequiredbodyrequiredhtmluser_idrequiredattachment_ids

enchant_create_customer

Create customer

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

Parameterssummarycontactslast_namefirst_name

enchant_update_customer

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

Parametersidrequiredsummarycontactslast_namefirst_name

enchant_add_customer_contact

Add customer contact

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

Parametersidrequiredtyperequiredvaluerequired

enchant_delete_customer_contact

Delete customer contact

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

Parametersidrequiredcontact_idrequired

Version history

19
  1. v1.23.3LatestNov 7, 2026
  2. v1.22.3Nov 5, 2026
  3. v1.22.2Nov 5, 2026
  4. v1.22.1Nov 4, 2026
  5. v1.22.0Nov 3, 2026
  6. v1.21.1Nov 3, 2026
  7. v1.20.0Nov 1, 2026
  8. v1.18.0Oct 31, 2026
  9. v1.17.0Oct 31, 2026
  10. v1.16.2Oct 30, 2026
  11. v1.16.0Oct 30, 2026
  12. v1.11.0Oct 26, 2026
  13. v1.8.3Oct 25, 2026
  14. v1.8.0Oct 25, 2026
  15. v1.7.0Oct 24, 2026
  16. v1.4.0Oct 23, 2026
  17. v1.3.4Oct 22, 2026
  18. v1.3.3Oct 21, 2026
  19. v1.0.0Oct 10, 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