io.usefulapi/enchant
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
Enchant MCP by usefulapi
Publisher-provided description
Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers.
Summary by lookupd
Lists, reads, creates and updates help desk tickets and customers, and can send email replies or add internal notes and labels.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http enchant https://enchant.usefulapi.io/mcp
Codex, remote (streamable-http)
codex mcp add enchant --url https://enchant.usefulapi.io/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"enchant": {
"url": "https://enchant.usefulapi.io/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (16 tools)
Publisher-provided text
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; usenchant_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 1enchant_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 bodyenchant_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 tenchant_add_ticket_labelsWRITE: add one or more labels to a ticket without changing its other labels. Enchant REST: PUT /tickets/{id}/labels/{label_ids}.enchant_remove_ticket_labelsWRITE: remove one or more labels from a ticket; its other labels stay. Enchant REST: DELETE /tickets/{id}/labels/{label_ids}.enchant_reply_to_ticketWRITE: 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: POSenchant_add_noteWRITE: add an internal note to a ticket (not sent to the customer). Enchant REST: POST /tickets/{id}/messages (type note).enchant_create_customerWRITE: create a customer with optional contacts (email, twitter, phone). Enchant REST: POST /customers.enchant_update_customerWRITE: 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: PATenchant_add_customer_contactWRITE: add one contact (email, twitter or phone) to a customer. Enchant REST: POST /customers/{id}/contacts.enchant_delete_customer_contactWRITE, DELETES DATA: remove one contact from a customer. Enchant REST: DELETE /customers/{id}/contacts/{contact_id}.
Details
- Version: 1.24.3
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 610 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/enchant/
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.usefulapi/enchant)
- 62092 servers
- Last crawl: 2026-11-11T17:17:22.074Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp