Enchant MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.3.3 · published by io.usefulapi

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

Deletes · 10

Compare Registry entry

16 tools: 10 can delete or cancel things and 6 only read.

Scanned Oct 21, 2026

Deletes or cancels10Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things0Claude Code: ask
Only reads6Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http enchant https://enchant.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

16 tools

Deletes or cancels 10Removes, cancels or revokes something.Claude Code: deny

enchant_add_customer_contactWRITE: add one contact (email, twitter or phone) to a customer.No findings
Why it is in this group
- The name "enchant_add_customer_contact" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: add one contact (email, twitter or phone) to a customer. Enchant REST: POST /customers/{id}/contacts.
Annotations the server declares
- title: Add customer contact
- destructiveHint: true
enchant_add_noteWRITE: add an internal note to a ticket (not sent to the customer).No findings
Why it is in this group
- The name "enchant_add_note" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: add an internal note to a ticket (not sent to the customer). Enchant REST: POST /tickets/{id}/messages (type note).
Annotations the server declares
- title: Add internal note
- destructiveHint: true
enchant_add_ticket_labelsWRITE: add one or more labels to a ticket without changing its other labels.No findings
Why it is in this group
- The name "enchant_add_ticket_labels" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: add one or more labels to a ticket without changing its other labels. Enchant REST: PUT /tickets/{id}/labels/{label_ids}.
Annotations the server declares
- title: Add labels to ticket
- destructiveHint: true
enchant_create_customerWRITE: create a customer with optional contacts (email, twitter, phone).No findings
Why it is in this group
- The name "enchant_create_customer" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: create a customer with optional contacts (email, twitter, phone). Enchant REST: POST /customers.
Annotations the server declares
- title: Create customer
- destructiveHint: true
enchant_create_ticketWRITE: create an email ticket.No findings
Why it is in this group
- The name "enchant_create_ticket" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Create ticket
- destructiveHint: true
enchant_delete_customer_contactWRITE, DELETES DATA: remove one contact from a customer.No findings
Why it is in this group
- The name "enchant_delete_customer_contact" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE, DELETES DATA: remove one contact from a customer. Enchant REST: DELETE /customers/{id}/contacts/{contact_id}.
Annotations the server declares
- title: Delete customer contact
- destructiveHint: true
enchant_remove_ticket_labelsWRITE: remove one or more labels from a ticket; its other labels stay.No findings
Why it is in this group
- The name "enchant_remove_ticket_labels" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: remove one or more labels from a ticket; its other labels stay. Enchant REST: DELETE /tickets/{id}/labels/{label_ids}.
Annotations the server declares
- title: Remove labels from ticket
- destructiveHint: true
enchant_reply_to_ticketWRITE: send an outbound reply on a ticket.No findings
Why it is in this group
- The name "enchant_reply_to_ticket" says "reply": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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).
Annotations the server declares
- title: Reply to customer
- destructiveHint: true
enchant_update_customerWRITE: update a customer's name or summary.No findings
Why it is in this group
- The name "enchant_update_customer" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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}.
Annotations the server declares
- title: Update customer
- destructiveHint: true
enchant_update_ticketWRITE: change a ticket: state (open, hold, closed), assignee, inbox, subject, spam or trash (not both true).No findings
Why it is in this group
- The name "enchant_update_ticket" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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}.
Annotations the server declares
- title: Update ticket
- destructiveHint: true

Only reads 6Looks things up and changes nothing.Claude Code: allow

enchant_get_attachmentGet the metadata of an attachment (name, size, MIME type) by id; attachment ids appear in ticket messages.No findings
Why it is in this group
- The name "enchant_get_attachment" says "get": a word for reading.
Description, as the server wrote it
Get the metadata of an attachment (name, size, MIME type) by id; attachment ids appear in ticket messages. Enchant REST: GET /attachments/{id}.
Annotations the server declares
- title: Get attachment
- readOnlyHint: true
enchant_get_customerGet one customer by id, with the contacts (emails, phones, Twitter names).No findings
Why it is in this group
- The name "enchant_get_customer" says "get": a word for reading.
Description, as the server wrote it
Get one customer by id, with the contacts (emails, phones, Twitter names). Enchant REST: GET /customers/{id}.
Annotations the server declares
- title: Get customer
- readOnlyHint: true
enchant_get_ticketGet one ticket by id.No findings
Why it is in this group
- The name "enchant_get_ticket" says "get": a word for reading.
Description, as the server wrote it
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}.
Annotations the server declares
- title: Get ticket
- readOnlyHint: true
enchant_list_customersList customers, or find one by contact: set contact_type and contact_value (for example email + an address).No findings
Why it is in this group
- The name "enchant_list_customers" says "list": a word for reading.
Description, as the server wrote it
List customers, or find one by contact: set contact_type and contact_value (for example email + an address). Enchant REST: GET /customers.
Annotations the server declares
- title: List customers
- readOnlyHint: true
enchant_list_ticketsList and filter tickets (newest first by default).No findings
Why it is in this group
- The name "enchant_list_tickets" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List tickets
- readOnlyHint: true
enchant_list_usersList the help desk users (agents): id, name, email.No findings
Why it is in this group
- The name "enchant_list_users" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List users (agents)
- readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.3.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http enchant https://enchant.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__enchant__enchant_list_tickets",
      "mcp__enchant__enchant_get_ticket",
      "mcp__enchant__enchant_list_users",
      "mcp__enchant__enchant_list_customers",
      "mcp__enchant__enchant_get_customer",
      "mcp__enchant__enchant_get_attachment"
    ],
    "ask": [],
    "deny": [
      "mcp__enchant__enchant_create_ticket",
      "mcp__enchant__enchant_update_ticket",
      "mcp__enchant__enchant_add_ticket_labels",
      "mcp__enchant__enchant_remove_ticket_labels",
      "mcp__enchant__enchant_reply_to_ticket",
      "mcp__enchant__enchant_add_note",
      "mcp__enchant__enchant_create_customer",
      "mcp__enchant__enchant_update_customer",
      "mcp__enchant__enchant_add_customer_contact",
      "mcp__enchant__enchant_delete_customer_contact"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as enchant. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/enchant/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

10 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:23 UTC.

For agents: Markdown · JSON · report this listing