Enchant MCP by usefulapi

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Last Tested: 2026-10-10 19:46
Transport: Streamable HTTP · MCP 2025-06-18
URL
Repository: m190/usefulapi-mcp
GitHub Stars: 0

TDQS

Score is being calculated.

Available Tools

16 tools

enchant_add_customer_contactAdd customer contact

Destructive

Inspect

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

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Customer id.
`type`	Yes	Contact type.
`value`	Yes	Email address, Twitter screen name or phone number.

enchant_add_noteAdd internal note

Destructive

Inspect

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

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Ticket id.
`body`	Yes	Note body.
`html`	No	True if body is HTML (default false: plain text).
`user_id`	Yes	Id of the user (agent) the note is from; see enchant_list_users.
`attachment_ids`	No	Ids of attachments already uploaded.

enchant_add_ticket_labelsAdd labels to ticket

Destructive

Inspect

WRITE: add one or more labels to a ticket without changing its other labels. Enchant REST: PUT /tickets/{id}/labels/{label_ids}.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Ticket id.
`label_ids`	Yes	Label ids to add.

enchant_create_customerCreate customer

Destructive

Inspect

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

ParametersJSON Schema

Name	Required	Description
`summary`	No	Short free-text summary shown on the customer profile.
`contacts`	No	Contacts of the customer.
`last_name`	No
`first_name`	No

enchant_create_ticketCreate ticket

Destructive

Inspect

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.

ParametersJSON Schema

Name	Required	Description
`body`	No	First inbound message from the customer (plain text).
`subject`	Yes	Ticket subject.
`user_id`	No	User id to assign the ticket to.
`customer`	No	Customer to find or create, instead of customer_id.
`inbox_id`	No	Inbox id (the default inbox if omitted).
`customer_id`	No	Existing customer id. Give this or customer.

enchant_delete_customer_contactDelete customer contact

Destructive

Inspect

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

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Customer id.
`contact_id`	Yes	Contact id (from the customer's contacts).

enchant_get_attachmentGet attachment

Read-only

Inspect

Get the metadata of an attachment (name, size, MIME type) by id; attachment ids appear in ticket messages. Enchant REST: GET /attachments/{id}.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Attachment id.

enchant_get_customerGet customer

Read-only

Inspect

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

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Customer id.

enchant_get_ticketGet ticket

Read-only

Inspect

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

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Ticket id (the string id, not the friendly ticket number).
`embed`	No	Related resources to embed.

enchant_list_customersList customers

Read-only

Inspect

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

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number (1-based). Past 10,000 results, filter by since_created_at instead.
`count`	No	If true, also return the total number of matching results (costs 1 extra rate-limit credit).
`per_page`	No	Results per page (0-100, default 10). Use 0 with count to get only the total.
`contact_type`	No	Contact type to match (use with contact_value).
`contact_value`	No	Email address or Twitter screen name to match (use with contact_type).
`since_created_at`	No	Only customers created since this UTC ISO 8601 time.

enchant_list_ticketsList tickets

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description
`ids`	No	Only these ticket ids.
`page`	No	Page number (1-based). Past 10,000 results, filter by since_created_at instead.
`sort`	No	Sort order; a leading - means descending.
`spam`	No	Only spam (true) or only non-spam (false) tickets.
`count`	No	If true, also return the total number of matching results (costs 1 extra rate-limit credit).
`trash`	No	Only trashed (true) or only non-trashed (false) tickets.
`types`	No	Ticket types, e.g. email, chat, sms, phone, web, twitter, whatsapp.
`states`	No	Only tickets in these states.
`per_page`	No	Results per page (0-100, default 10). Use 0 with count to get only the total.
`user_ids`	No	Only tickets assigned to these user ids ("null" = unassigned).
`inbox_ids`	No	Only tickets in these inbox ids.
`label_ids`	No	Only tickets with these label ids.
`since_created_at`	No	Only tickets created since this UTC ISO 8601 time, e.g. 2026-01-31T13:41:10Z.
`since_updated_at`	No	Only tickets updated since this UTC ISO 8601 time.

enchant_list_usersList users (agents)

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`page`	No	Page number (1-based). Past 10,000 results, filter by since_created_at instead.
`per_page`	No	Results per page (0-100, default 10). Use 0 with count to get only the total.

enchant_remove_ticket_labelsRemove labels from ticket

Destructive

Inspect

WRITE: remove one or more labels from a ticket; its other labels stay. Enchant REST: DELETE /tickets/{id}/labels/{label_ids}.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Ticket id.
`label_ids`	Yes	Label ids to remove.

enchant_reply_to_ticketReply to customer

Destructive

Inspect

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

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Ticket id.
`to`	Yes	Recipient address, normally the customer's email.
`body`	Yes	Reply body.
`html`	No	True if body is HTML (default false: plain text).
`user_id`	Yes	Id of the user (agent) the reply is sent as; see enchant_list_users.
`attachment_ids`	No	Ids of attachments already uploaded.

enchant_update_customerUpdate customer

Destructive

Inspect

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

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Customer id.
`summary`	No	Short free-text summary shown on the customer profile.
`contacts`	No	The full new contact list (replaces the existing one).
`last_name`	No
`first_name`	No

enchant_update_ticketUpdate ticket

Destructive

Inspect

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

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Ticket id.
`spam`	No	Mark as spam. Cannot be true together with trash.
`state`	No	New state.
`trash`	No	Send to trash. Cannot be true together with spam.
`subject`	No	New subject.
`user_id`	No	Assign to this user id; null unassigns the ticket.
`inbox_id`	No	Move to this inbox id.
`label_ids`	No	The full new set of label ids (replaces existing labels).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

16 tool updatesOct 10, 2026
- First observedenchant_add_customer_contact
- First observedenchant_add_note
- First observedenchant_add_ticket_labels
- First observedenchant_create_customer
- First observedenchant_create_ticket
- First observedenchant_delete_customer_contact
- First observedenchant_get_attachment
- First observedenchant_get_customer
- First observedenchant_get_ticket
- First observedenchant_list_customers
- First observedenchant_list_tickets
- First observedenchant_list_users
- First observedenchant_remove_ticket_labels
- First observedenchant_reply_to_ticket
- First observedenchant_update_customer
- First observedenchant_update_ticket

Related MCP Connectors

Freshdesk MCP by usefulapi A
io.usefulapi
Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
Customer Support CRM
191
eDesk MCP by usefulapi
io.usefulapi
Work with eDesk support tickets, replies, internal notes, contacts and sales orders.
1
Trengo MCP by usefulapi A
io.usefulapi
Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.
Customer Support Communication CRM
241
Zendesk MCP by usefulapi A
io.usefulapi
Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.
Customer Support CRM
191

Related MCP Servers

zendesk-mcp
Customer Support Project Management
michaelrice
A
license
A
quality
A
maintenance
Enables reading and writing Zendesk tickets, including searching, fetching comments, posting replies and internal notes, setting ticket status, assigning tickets, logging time, and formatting tickets as Markdown issue drafts for handoff to GitLab, GitHub, or Jira.
Updated 2 days ago (2026-10-08 19:37 UTC)
29
273 PyPI
7
Apache 2.0
mcp-tomticket
Customer Support Communication
glira
A
license
B
quality
B
maintenance
TomTicket helpdesk MCP: list, reply, log time, and finish tickets plus customers, chats, and knowledge base.
Updated 2 months ago (2026-08-21 18:03 UTC)
49
23 npm
MIT
Xalantis MCP Serverofficial
Customer Support App Automation
xalantis-hub
A
license
A
quality
B
maintenance
Enables managing support tickets from Claude, Cursor, and other AI tools, including listing, creating, updating, and replying to tickets.
Updated 2 months ago (2026-07-28 21:04 UTC)
6
8 npm
MIT
Alex's Zendesk MCP Server
Customer Support
aleburbridge
F
license
Not graded
quality
D
maintenance
Enables interaction with Zendesk to manage tickets, retrieve ticket fields, comments, and priority based on SLA, as well as get unsolved tickets by agent name.
Updated a year ago (2025-07-28 14:38 UTC)
1
-