# Enchant MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Enchant MCP

Manage help desk tickets, customers, and replies in Enchant directly from Muse.

- Record: https://musedirectory.ai/connector/enchant-mcp
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/enchant/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 1739ms, checked 2026-10-29T09:16:10Z
- Endpoint: https://enchant.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T12:46:29Z)
- Source: Found in the official MCP Registry (io.usefulapi/enchant) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fenchant

Connect to Enchant help desk to list and search tickets, read conversations, reply to customers, add internal notes, manage labels and customer records. Requires an Enchant account and API access.

Example request: "Show me all open support tickets assigned to me and let me reply to the most recent one."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Enchant MCP to help me. It is a free service with an MCP server at https://enchant.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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_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: 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: 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: Get one customer by id, with the contacts (emails, phones, Twitter names). Enchant REST: GET /customers/{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_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: 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 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 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_add_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 a customer with optional contacts (email, twitter, phone). Enchant REST: POST /customers.
- 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_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, DELETES DATA: remove one contact from a customer. Enchant REST: DELETE /customers/{id}/contacts/{contact_id}.

Screening checks:
- MCP handshake: pass (Answered in 287ms)
- Domain against threat feeds (Cloudflare security DNS): pass (enchant.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (16 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)