Dixa MCP server

What the model can do

Dixa customer service: search conversations by text, status, queue, agent and date, read a conversation's messages, internal notes and ratings, find end users and their conversations, list agents, queues, tags, custom attributes and email endpoints. Can reply to a customer, start an email conversation, add internal notes, close, reopen, transfer, claim, tag or follow up a conversation, set its custom attributes, offer a rating, create tags, and create, update or anonymise end users.

Reads

• dixa_search_conversationsSearch Dixa conversations by words in them and by status, queue, assigned agent, creation date or last activity; each hit is read in full (channel…
• dixa_get_conversationOne Dixa conversation by its number, with its messages (oldest first, the last ones if long), internal notes and CSAT/NPS ratings.
• dixa_find_end_usersFind Dixa end users (customers) by exact email, phone number or your own external id: id, display name, created.
• dixa_end_user_conversationsConversations of one Dixa end user (by the id from dixa_find_end_users): channel, state, subject, created, assigned agent and queue.
• dixa_list_agentsDixa agents: id, display name and roles.
• dixa_list_queuesDixa queues: id, name and whether it is the default.
• dixa_list_tagsDixa conversation tags: id, name and state.
• dixa_list_custom_attributesDixa custom attribute definitions: id, label, identifier, whether for conversations or contacts, input type, required, archived.
• dixa_list_email_endpointsThe organisation's Dixa email addresses (contact endpoints).

Acts, when you ask

These change something in Dixa. 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.

• dixa_add_internal_noteAdd an internal note to a Dixa conversation.
• dixa_reply_to_conversationSends a message to the customer in a Dixa conversation, written as the agent you name (dixa_list_agents…
• dixa_start_email_conversationStarts a new Dixa email conversation with an end user (dixa_find_end_users or dixa_create_end_user) from one of the organisation's email addresses…
• dixa_close_conversationCloses a Dixa conversation, as the agent you name or Dixa's System User if none.
• dixa_reopen_conversationReopens a closed Dixa conversation and offers it to agents in its queue (or the default queue).
• dixa_transfer_conversationTransfers a Dixa conversation to another queue (dixa_list_queues), where its agents are offered it.
• dixa_claim_conversationAssigns a Dixa conversation to an agent.
• dixa_tag_conversationAdds an active tag (dixa_list_tags) to a Dixa conversation, or removes a tag with remove true.
• dixa_follow_up_conversationSets a follow-up on a Dixa conversation, which comes back to an agent at the given future time.
• dixa_set_conversation_attributesSets custom attribute values on a Dixa conversation: a text value, or a list of options for a select attribute (ids from dixa_list_custom_attributes…
• dixa_offer_ratingOffers a satisfaction rating (Csat, Nps or ThumbsUpOrDown) to the end user on a Dixa conversation, attributed to an agent on that conversation.
• dixa_create_tagCreates a Dixa conversation tag with a name and optional colour.
• dixa_create_end_userCreates a Dixa end user (a customer record) with a display name, first and last name, email or your own external id.
• dixa_update_end_userUpdates a Dixa end user's display name, first or last name, primary email or external id.
• dixa_anonymize_end_userRequests permanent anonymisation of a Dixa end user (a GDPR erasure): their personal data is removed and cannot be restored.

Connect it

First connect Dixa on Dashboard → Connections, then add Memtro to your client once. The Dixa 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 Dixa 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

• › What did Acme contact support about last week?
• › Which conversations in the billing queue are still open?
• › How did the customer rate the conversation Priya Nair handled yesterday?
• › Reply to conversation 4812 as Priya that the refund went out today
• › Transfer the Globex conversation to the billing queue

Questions

Is this an official Dixa MCP server?

No. It is Memtro's MCP server with Memtro's Dixa connector behind it: the connector reads Dixa through its API with the credentials you connect on Dashboard → Connections, and Dixa 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 Dixa?

Only when you ask, and only what it has been granted: add an internal note to a conversation, never sent to the customer; reply to the customer in a conversation as a named agent; start an email conversation with a customer (the first message is emailed); close a conversation; reopen a conversation in its queue; transfer a conversation to another queue; assign (claim) a conversation for an agent; add or remove a tag on a conversation; set a follow-up time on a conversation; set custom attribute values on a conversation; offer a satisfaction rating to the customer; create a conversation tag; create an end user (customer record); update an end user's name, email or external id; anonymise an end user (permanent erasure). 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