Enchant MCP server

What the model can do

Enchant shared inbox: tickets by state, inbox, assignee, label and date, a ticket with its messages and customer, the help desk's agents, and customers found by email; when you ask, can add an internal note, email a reply to the customer, open a ticket, change a ticket's state, assignee, inbox or subject, mark it spam or trash, add or remove labels, and create or edit customers and their contacts.

Reads

• enchant_list_ticketsList Enchant tickets, newest first unless sorted otherwise: subject, state, channel, assignee, inbox, customer id, labels and the opening summary.
• enchant_get_ticketRead one Enchant ticket with its messages (replies and internal notes, oldest first, bodies cut at 2,000 characters) and, if asked…
• enchant_list_usersList the agents (users) of the Enchant help desk with their ids, names and emails.
• enchant_list_customersList Enchant customers, newest first, or find one by email address.
• enchant_get_customerRead one Enchant customer by id: name, email addresses, summary note, and the types of their other contacts.

Acts, when you ask

These change something in Enchant. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• enchant_add_noteAdds an internal note to an Enchant ticket, written as the agent you name.
• enchant_reply_to_customerEmails a reply to the customer on an Enchant ticket, from the help desk, as the agent you name, to the address you give.
• enchant_create_ticketOpens a new email ticket in Enchant for a customer, by customer id or by name and email (Enchant finds the customer by email, or creates one).
• enchant_update_ticketChanges an Enchant ticket: its state (open, hold or closed), assignee, inbox or subject, or marks it spam or trash (soft flags…
• enchant_add_labelsAdds labels to an Enchant ticket, keeping the labels it has.
• enchant_remove_labelsRemoves labels from an Enchant ticket; the labels themselves are not deleted.
• enchant_create_customerCreates a customer in Enchant with a name, a summary note and contacts.
• enchant_update_customerChanges an Enchant customer's name or summary note.
• enchant_add_customer_contactAdds an email address, phone number or Twitter handle to an Enchant customer.
• enchant_delete_customer_contactPermanently deletes one contact (an email, phone or Twitter entry) from an Enchant customer…

Connect it

First connect Enchant on Dashboard → Connections, then add Memtro to your client once. The Enchant tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Enchant connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which Enchant tickets are open and unassigned?
• › What has the customer said on ticket 4821 so far?
• › Which tickets labelled refund are on hold?
• › Which agents are on the help desk?
• › Add an internal note to ticket 4821 saying the replacement has shipped.

Questions

Is this an official Enchant MCP server?

No. It is Memtro's MCP server with Memtro's Enchant connector behind it: the connector reads Enchant through its API with the credentials you connect on Dashboard → Connections, and Enchant publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Enchant?

Only when you ask, and only what it has been granted: add an internal note to a ticket; email a reply to the customer on a ticket; open a new email ticket for a customer; change a ticket's state, assignee, inbox or subject, or mark it spam or trash; add labels to a ticket; remove labels from a ticket; create a customer; change a customer's name, summary or contacts; add an email, phone or Twitter contact to a customer; delete a contact from a customer. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Support

• Help Scout MCP server
• Zendesk MCP server
• Intercom MCP server
• Freshdesk MCP server
• Front MCP server
• Zoho Desk MCP server