Enchant MCP by usefulapi
by FastDrop
Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers.
Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers. Official MCP Registry: io.usefulapi/enchant@1.0.0. Remote endpoint: https://enchant.usefulapi.io/mcp
Problem it solves
Discoverable MCP server listed in the official MCP Registry.
How it's different
Remote MCP endpoint ingested from the official registry and probed by FastDrop.
Ingested from the official MCP Registry
FastDrop pulled this entry from the official MCP Registry as io.usefulapi/enchant and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed
and the description is not theirs.
If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.
Claim this listingTools this endpoint exposes
Read directly from the endpoint on 10 Oct 2026. Not supplied by the maker.
enchant_list_ticketsList 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_ticketGet 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:
enchant_list_usersList 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_customersList customers, or find one by contact: set contact_type and contact_value (for example email + an address). Enchant REST: GET /customers.
enchant_get_customerGet one customer by id, with the contacts (emails, phones, Twitter names). Enchant REST: GET /customers/{id}.
enchant_get_attachmentGet the metadata of an attachment (name, size, MIME type) by id; attachment ids appear in ticket messages. Enchant REST: GET /attachments/{id}.
enchant_create_ticketWRITE: 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 R
enchant_update_ticketWRITE: 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 k
Is this tool yours?
Claim this listing and we’ll verify ownership before handing it over.
Sign in to claim this listingSimilar launches
Matched on shared tags and the tools their MCP servers actually expose.
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Reviews
Sign in to leave a review.
No reviews yet.
Comments
Sign in to join the discussion.
No comments yet - start the discussion.