--- title: "Dixa MCP server for AI agents - actionlake" description: "Give Claude 125 Dixa actions through one MCP server: conversations, agents. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/dixa updated: 2026-10-23 --- Connectors · Service desk & support # Dixa MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Dixa and the rest of your systems. It gives your agent 125 Dixa actions (63 reads, 47 writes and 15 that wait for a confirmation) and holds the Dixa credential itself, so the agent never does. It paces Dixa's limits and records every call. [Connect Dixa free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "dixa.agents.list", intent: "check which Dixa account is connected" } # List agents · read · 1 upstream call ``` - 125 actions in one signed file - 63 read look, never change - 47 write create and update - 15 wait for a yes destructive, confirmed first Set up ## Connect Dixa in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Dixa. Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `api_token` Dixa API token: in Dixa go to Settings > Integrations > API tokens and add an API token (Dixa API version 1) ``` account { op: "connections.requirements", service: "dixa" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "dixa.agents.list" } # list agents · read · 1 upstream call check { action: "dixa.agents.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Dixa at a glance **Sign-in** Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `api_token` **Limits we pace to** 10 calls a second, per connection **API covered** Dixa API v1 (OpenAPI 3.0.3) and Dixa Exports API v1`dev.dixa.io` **Built from** Dixa's documentation, read 23 October 2026[docs.dixa.io](https://docs.dixa.io/openapi-specs/dixa-v1.json) [docs.dixa.io](https://docs.dixa.io/openapi-specs/exports.json) [docs.dixa.io](https://docs.dixa.io/docs/api-standards-rules) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 60 of 63 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 6, so ask can line Dixa up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Dixa. 125 actions in 27 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **63** read look, never change - **47** write create and update - **15** destructive wait for a confirmation 1. ### Conversations 16 6 read · 9 write · 1 destructive Create conversation · Get conversation · Search conversations · Claim conversation 2. ### Agents 13 5 read · 7 write · 1 destructive List agents · Create agent · Get agent · Patch agent 3. ### Knowledge articles 13 2 read · 8 write · 3 destructive Create article · Get article · Update article · Delete article 4. ### Endusers 11 3 read · 7 write · 1 destructive List end users · Create end user · Get end user · Patch end user 5. ### Queues 8 5 read · 2 write · 1 destructive List queues · Create queue · Get queue · List agents 6. ### Teams 8 4 read · 2 write · 2 destructive List teams · Create team · Get team · Delete team 7. ### Webhooks 7 4 read · 2 write · 1 destructive Create Webhook Subscription · List all Webhook Subscriptions · Webhook Subscription Event Logs · Webhook Subscription 8. ### Tags 6 2 read · 3 write · 1 destructive List tags · Create tag · Get tag · Delete tag **19 more areas · 43 actions** - Business hours schedules **4** - Conversation ratings **4** - Conversation tags **4** - Analytics metrics **3** - Analytics records **3** - Conversation messages **3** - Conversation notes **3** - Knowledge collections **3** - Anonymization requests **2** - Contact endpoints **2** - Custom attributes **2** - Knowledge categories **2** - Templates **2** - AI agents **1** - Analytics filters **1** - Conversation exports **1** - Conversation flows **1** - Message exports **1** - Organization **1** Top actions ## The Dixa API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 36 of Dixa's 36 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `dixa.agents.list` List agents | List agents. | read | `identity.user.list` 474 connectors | | `dixa.teams.list` List teams | List teams. | read | `identity.group.list` 262 connectors | | `dixa.agents.create` Create agent | Create agent. | write | `identity.user.create` 262 connectors | | `dixa.teams.create` Create team | Create team. | write | `identity.group.create` 205 connectors | | `dixa.endusers.list` List end users | List end users. | read | `crm.contact.list` 177 connectors | | `dixa.agents.delete` Delete agent | Delete agent. | destructive | `identity.user.delete` 253 connectors | | `dixa.queues.list` List queues | List queues. | read | `service.queue.list` 21 connectors | | `dixa.conversation_exports.list` Returns a list of conversations. | Returns a list of conversations. | read | `service.conversation.list` 19 connectors | | `dixa.tags.list` List tags | List tags. | read | `crm.tag.list` 65 connectors | | `dixa.endusers.create` Create end user | Create end user. | write | `crm.contact.create` 161 connectors | | `dixa.queues.create` Create queue | Create queue. | write | `service.queue.create` 14 connectors | | `dixa.conversations.create` Create conversation | Create conversation. | write | `service.conversation.create` 13 connectors | Try it ## Prompts to paste into Claude. Each one names the Dixa actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Find the Dixa contacts with no email address, so we can clean them up. calls `dixa.endusers.list` 2. Write write Create agent in Dixa. Show me exactly what you will send before you save it. calls `dixa.agents.create` 3. Across systems read Which contacts are in both Dixa and HaloPSA, and how many are in only one of them? calls `dixa.endusers.list` `halopsa.users.list` Across your systems ## Dixa, joined to the rest of your business. One `ask` fetches from Dixa and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row. - Which contacts are in both Dixa and HaloPSA, and how many are in only one of them? `dixa.endusers.list` + `halopsa.users.list`, on `crm.contact` · [HaloPSA](https://actionlake.com/connectors/halopsa) - Which contacts are in both Dixa and NetSuite, and how many are in only one of them? `dixa.endusers.list` + `netsuite.views.contacts`, on `crm.contact` · [NetSuite](https://actionlake.com/connectors/netsuite) Also mapped by other connectors `identity.user` **517** `identity.group` **239** `crm.contact` **192** `crm.tag` **47** `service.queue` **14** `service.conversation` **12** ask ``` ask { intent: "which contacts are in both Dixa and HaloPSA, and how many are in only one of them", steps: [ { action: "dixa.endusers.list", as: "people", input: {}, limit: 100, max_pages: 5 }, { action: "halopsa.users.list", as: "people2", input: {}, limit: 100, max_pages: 5 }, { join: { left: "people", right: "people2", on: "crm.contact", group_by: "people.email", select: ["people.email", "count(people2.id) as in_halopsa"] } } ] } ``` Example. Run it through check first: it validates the steps and prices them, and it is free. Governance for Dixa ## Destructive actions wait for a yes. 15 Dixa actions are destructive. These are all of them: - Delete agent `dixa.agents.delete` - Delete team `dixa.teams.delete` - Remove members `dixa.teams.remove_agents` - Delete tag `dixa.tags.delete` - Delete article `dixa.knowledge_articles.delete` - Anonymize end user `dixa.endusers.anonymize` - Remove agents `dixa.queues.remove_members` - Anonymize conversation `dixa.conversations.anonymize` - Anonymize message `dixa.conversation_messages.anonymize` - Remove article parent `dixa.knowledge_articles.remove_parent` - Delete article translation `dixa.knowledge_articles.delete_translation` - Delete Webhook Subscription `dixa.webhooks.delete` - Delete template `dixa.templates.delete` - Untag conversation `dixa.conversation_tags.remove` - Anonymize entity `dixa.anonymization_requests.create` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do dixa.agents.delete confirm_policy: **human** Delete agent? **intent:** the user asked me to delete agent run suspended · waiting for a named person · key _dixa-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "dixa-agent", allowed_actions: ["dixa.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "dixa.agents.delete", approver: "lead@example.com" }, { match: "dixa.teams.delete", approver: "lead@example.com" }, { match: "dixa.teams.remove_agents", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Dixa only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Dixa costs on actionlake. Every Dixa action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Dixa refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 125 Dixa actions - 125 actions page each page of a long list is one call - 60 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Dixa action. 125 actions by area: the id your agent calls, what it does, and its effect. **Conversations 16** - `dixa.conversations.anonymize` Anonymize conversation destructive - `dixa.conversations.claim` Claim conversation write - `dixa.conversations.close` Close conversation write - `dixa.conversations.create` Create conversation write - `dixa.conversations.follow_up` Followup conversation write - `dixa.conversations.get` Get conversation read - `dixa.conversations.get_activity_log` List activity log read - `dixa.conversations.import` Import conversation write - `dixa.conversations.link` Link a conversation to a parent conversation write - `dixa.conversations.list_activity_log` List organization activity log read - `dixa.conversations.list_linked` List linked conversations read - `dixa.conversations.patch_custom_attributes` Patch conversation custom attributes write - `dixa.conversations.reopen` Reopen conversation write - `dixa.conversations.search` Search conversations with filters read - `dixa.conversations.search_text` Search conversations read - `dixa.conversations.transfer_to_queue` Transfer conversation write **Agents 13** - `dixa.agents.bulk_create` Create agents write - `dixa.agents.bulk_patch` Patch agents write - `dixa.agents.bulk_replace` Update agents write - `dixa.agents.create` Create agent write - `dixa.agents.delete` Delete agent destructive - `dixa.agents.get` Get agent read - `dixa.agents.get_presence` Get presence read - `dixa.agents.list` List agents read - `dixa.agents.list_presence` List presence read - `dixa.agents.list_teams` List teams read - `dixa.agents.replace` Update agent write - `dixa.agents.set_working_channel` Updates the working channel of an agent write - `dixa.agents.update` Patch agent write **Knowledge articles 13** - `dixa.knowledge_articles.create` Create article write - `dixa.knowledge_articles.delete` Delete article destructive - `dixa.knowledge_articles.delete_translation` Delete article translation destructive - `dixa.knowledge_articles.get` Get article read - `dixa.knowledge_articles.list_translations` Get article translations read - `dixa.knowledge_articles.publish` Publish article write - `dixa.knowledge_articles.publish_translation` Publish translation write - `dixa.knowledge_articles.remove_parent` Remove article parent destructive - `dixa.knowledge_articles.set_parent` Move article write - `dixa.knowledge_articles.unpublish` Unpublish article write - `dixa.knowledge_articles.unpublish_translation` Unpublish translation write - `dixa.knowledge_articles.update` Update article write - `dixa.knowledge_articles.update_translations` Update article translations write **Endusers 11** - `dixa.endusers.anonymize` Anonymize end user destructive - `dixa.endusers.bulk_create` Create end users write - `dixa.endusers.bulk_patch` Patch end users write - `dixa.endusers.bulk_replace` Update end users write - `dixa.endusers.create` Create end user write - `dixa.endusers.get` Get end user read - `dixa.endusers.list` List end users read - `dixa.endusers.list_conversations` List end user conversations read - `dixa.endusers.patch_custom_attributes` Patch end user custom attributes write - `dixa.endusers.replace` Update end user write - `dixa.endusers.update` Patch end user write **Queues 8** - `dixa.queues.add_members` Assign agents write - `dixa.queues.check_availability` Get queue availability read - `dixa.queues.create` Create queue write - `dixa.queues.get` Get queue read - `dixa.queues.get_conversation_position` Get the position of the conversation in its current queue read - `dixa.queues.list` List queues read - `dixa.queues.list_members` List agents read - `dixa.queues.remove_members` Remove agents destructive **Teams 8** - `dixa.teams.add_agents` Add members write - `dixa.teams.create` Create team write - `dixa.teams.delete` Delete team destructive - `dixa.teams.get` Get team read - `dixa.teams.list` List teams read - `dixa.teams.list_agents` List members read - `dixa.teams.list_presence` List presence read - `dixa.teams.remove_agents` Remove members destructive **Webhooks 7** - `dixa.webhooks.create` Create Webhook Subscription write - `dixa.webhooks.delete` Delete Webhook Subscription destructive - `dixa.webhooks.get` Webhook Subscription read - `dixa.webhooks.get_delivery_status` Webhook Subscription Last Delivery Statuses read - `dixa.webhooks.list` List all Webhook Subscriptions read - `dixa.webhooks.list_delivery_logs` Webhook Subscription Event Logs read - `dixa.webhooks.update` Patch Webhook Subscription write **Tags 6** - `dixa.tags.activate` Activate tag write - `dixa.tags.create` Create tag write - `dixa.tags.deactivate` Deactivate tag write - `dixa.tags.delete` Delete tag destructive - `dixa.tags.get` Get tag read - `dixa.tags.list` List tags read **Business hours schedules 4** - `dixa.business_hours_schedules.get_definition` Get a business hours schedule definition. read - `dixa.business_hours_schedules.get_status` Check if a business is open read - `dixa.business_hours_schedules.list` List business hours schedules read - `dixa.business_hours_schedules.list_upcoming` Get the upcoming business hours schedule. read **Conversation ratings 4** - `dixa.conversation_ratings.get` List rating read - `dixa.conversation_ratings.list` List ratings for a conversation read - `dixa.conversation_ratings.offer` Create conversation rating offer write - `dixa.conversation_ratings.submit` Create conversation rating result write **Conversation tags 4** - `dixa.conversation_tags.add` Tag conversation write - `dixa.conversation_tags.bulk_add` Bulk tag conversation write - `dixa.conversation_tags.list` List tags read - `dixa.conversation_tags.remove` Untag conversation destructive **Analytics metrics 3** - `dixa.analytics_metrics.get` Metric Description read - `dixa.analytics_metrics.list` Metrics Catalogue read - `dixa.analytics_metrics.query` Get Metric Data read **Analytics records 3** - `dixa.analytics_records.get` Metric Record Description read - `dixa.analytics_records.list` Metric Records Catalogue read - `dixa.analytics_records.query` Get Metric Records Data read **Conversation messages 3** - `dixa.conversation_messages.anonymize` Anonymize message destructive - `dixa.conversation_messages.create` Add message write - `dixa.conversation_messages.list` List messages read **Conversation notes 3** - `dixa.conversation_notes.bulk_create` Add internal notes write - `dixa.conversation_notes.create` Add internal note write - `dixa.conversation_notes.list` List internal notes read **Knowledge collections 3** - `dixa.knowledge_collections.get` Get collection read - `dixa.knowledge_collections.get_catalog` Get collection catalog read - `dixa.knowledge_collections.list` List collections read **Anonymization requests 2** - `dixa.anonymization_requests.create` Anonymize entity destructive - `dixa.anonymization_requests.get` Get anonymization status read **Contact endpoints 2** - `dixa.contact_endpoints.get` Get contact endpoint read - `dixa.contact_endpoints.list` List contact endpoints read **Custom attributes 2** - `dixa.custom_attributes.get` Get custom attribute definition by id read - `dixa.custom_attributes.list` List custom attributes definitions read **Knowledge categories 2** - `dixa.knowledge_categories.get` Get category read - `dixa.knowledge_categories.list_translations` Get category translations read **Templates 2** - `dixa.templates.delete` Delete template destructive - `dixa.templates.list` List templates read **AI agents 1** - `dixa.ai_agents.list` List AI agents read **Analytics filters 1** - `dixa.analytics_filters.list_values` Filter values read **Conversation exports 1** - `dixa.conversation_exports.list` Returns a list of conversations. read **Conversation flows 1** - `dixa.conversation_flows.list` List flows read **Message exports 1** - `dixa.message_exports.list` Returns a list of messages. read **Organization 1** - `dixa.organization.get` Get organization details read Questions ## The Dixa MCP server, answered. **Is there a Dixa MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 125 Dixa actions across conversations, agents, knowledge articles and endusers, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Dixa. **What do I need to connect Dixa?** Dixa API token: in Dixa go to Settings > Integrations > API tokens and add an API token (Dixa API version 1). The free call account { op: "connections.requirements", service: "dixa" } lists exactly what to paste. **Can an AI agent delete or change things in Dixa?** Only if its key allows it, and only with an explicit confirmation. 15 Dixa actions are destructive, including delete agent, delete team and remove members. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Dixa API limit?** actionlake paces every call to the limits in the Dixa service file: 10 calls a second per connection. Repeated reads are answered from cache (60 Dixa actions can be), which never reaches Dixa. **What does a Dixa action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (125 Dixa actions page). Cache hits, searches, dry runs and calls Dixa refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Dixa API does it cover?** The Dixa API v1 (OpenAPI 3.0.3) and Dixa Exports API v1 at dev.dixa.io. It is built from Dixa's documentation as read on 23 October 2026. 125 actions in 27 areas, each one in the signed service file (version 1.0.0). **Can I combine Dixa with my other systems?** Yes. ask joins Dixa to HaloPSA or NetSuite on the same customer and returns the answer rather than every row. Dixa maps crm.contact, which 192 other connectors also map. **Does actionlake keep my Dixa data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Dixa credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Dixa Shares the most action names with - [Front 20](https://actionlake.com/connectors/front) - [Gorgias 17](https://actionlake.com/connectors/gorgias) - [Help Scout 14](https://actionlake.com/connectors/help-scout) - [Zoho Desk 13](https://actionlake.com/connectors/zoho-desk) - [Freshworks Freshchat 12](https://actionlake.com/connectors/freshworks-freshchat) - [LiveChat (Text platform) 12](https://actionlake.com/connectors/livechat-text-platform) Joins with, on shared entities - [Chatwoot 6](https://actionlake.com/connectors/chatwoot) - [Odoo 5](https://actionlake.com/connectors/odoo) - [Zoho SalesIQ 5](https://actionlake.com/connectors/zoho-salesiq) - [Intercom 5](https://actionlake.com/connectors/intercom) - [Crisp 5](https://actionlake.com/connectors/crisp) - [Genesys Cloud CX 4](https://actionlake.com/connectors/genesys-cloud-cx) Browse - [All Service desk & support connectors](https://actionlake.com/connectors/category/service-desk-and-support) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Dixa; the name is the vendor's own. Counts are from the Dixa service file, version 1.0.0. ## Give your agent Dixa today. [Connect Dixa free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/dixa More: https://actionlake.com/llms.txt