Axiom MCP connector
The Axiom connector lets Claude, ChatGPT, Cursor, or the Elaichi Agent query your logs and metrics, read dashboards, and check monitors, with each person signed in as themselves and every call recorded in an audit log.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
31 tools
How to connect
How to connect Axiom to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Axiom once
-
Open Connections, choose Add connection, and pick Axiom.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Axiom. Axiom's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Axiom MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Axiom MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Axiom MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Axiom to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Axiom through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Find the error behind a customer report
Ask what happened in a dataset around the time a customer reported a failure and get the matching log lines back in plain language.
-
On-call
Check which monitors are firing right now
Before a handover, ask for the monitors currently in alarm and their recent history so the next person starts with the full picture.
-
Support
Confirm an outage before replying to a ticket
Ask whether requests for a given account failed in the last hour, then reply to the customer with what actually happened.
-
Product
Build a dashboard for a new feature
Describe the charts you want, such as sign-ups by region or latency over the last day, and have the dashboard created in Axiom.
-
Security
Trace suspicious activity across datasets
Ask which datasets hold authentication logs, then query them for repeated failed logins from one address over the past week.
-
Platform
Set up a monitor for a new service
Ask for a monitor that fires when error rates cross a threshold and routes to the team's existing notifier.
Try asking
- “Which monitors fired in the last 24 hours?”
- “Show error counts by service from the production dataset today.”
- “Create a dashboard for checkout latency over the past week.”
Compare
Elaichi vs Zapier MCP vs Composio for Axiom
All three can connect Axiom to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Axiom tools | Allow or restrict single Axiom tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Axiom call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Axiom tools for your AI agents
31 tools are ready to call through Elaichi's MCP endpoint the moment you connect Axiom, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Axiom builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Axiom gets you
6 screens from the product, each doing one job for your Axiom account.
The agent
Ask Axiom a question and get an answer.
Query datasets, check monitors, and read dashboards by typing what you want to know.
- datasets
- dashboards
- monitors
- metrics
Ask Elaichi to work across your apps.
Which monitors fired in the last 24 hours?
Show error counts by service from the production dataset today.
Create a dashboard for checkout latency over the past week.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects Axiom to every client.
Claude, ChatGPT, and Cursor reach Axiom through one endpoint, no SDK and no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
31 Axiom tools, ready without writing code.
Datasets, metrics, dashboards, monitors, and notifiers are covered without any custom code.
- Query dataset
- Get saved queries
- List datasets
- Get dataset fields
ElaichiToolsToolboxes
Each team gets its own Axiom toolbox.
Scope toolboxes to on-call, platform, and support so each team sees only what it needs.
- Engineering
- On-call
- Platform
- Support
ElaichiToolboxesShared connections
Share an Axiom connection without sharing a credential.
One person connects Axiom, teammates work through it, and nobody else handles a token.
- Production
- Staging
- On-call
- Platform
ElaichiConnectionsAudit log
Every Axiom query is logged with a name.
See who ran which query, changed which dashboard, or deleted which monitor, and when.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts the Axiom digest itself.
Monitor history is fetched, grouped, drafted into a digest, approved by a person, then posted back.
Axiom digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch datasets
Axiom
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Axiom
Queued
Collections and dashboards
Axiom health numbers arrive without asking.
Four metrics, a 14 day chart, and a team breakdown, refreshed on a schedule, no model.
Axiom health
Refreshed 4 minutes ago · every 15 minutes · from the datasets collection
Datasets
1,284 ↓ 12%
Dashboards
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Datasets created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
On-call 21%
Platform 18%
FAQ
Frequently asked questions
How do I connect Axiom to Claude?
Connect Axiom in Elaichi first. Axiom connects over OAuth, so you sign in to Axiom and approve access, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and can start querying Axiom.
Does Axiom work with ChatGPT and Cursor as well as Claude?
Yes. Once Axiom is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Axiom once and every client uses it.
What can an AI agent actually do with my Axiom data?
An agent connected to Axiom can list your datasets and their fields, run queries against them, reuse saved queries, and search and query metrics. It can list, read, export, build, and edit dashboards, check which monitors are firing and their history, and create or update monitors that route to your notifiers. Short concrete asks, like which monitors fired overnight, work better than long sentences.
Does connecting Axiom give the AI access to every dataset in my organization?
No. Every call to Axiom runs as the person who signed in, so the AI sees only the datasets, dashboards, and monitors that person can already see in Axiom. Elaichi can narrow that access further for a team or a role, but it can never widen it beyond what Axiom already grants.
Can I stop an agent from deleting or changing things in Axiom?
Yes. Restrictions in Elaichi apply per action, so you can allow querying Axiom datasets while blocking the deletion of dashboards or monitors. A restricted action is never advertised to the AI client at all, so no prompt can reach it.
What happens to an Axiom connection when someone leaves?
Offboarding a person in Elaichi ends their access to Axiom through every client at once. A shared Axiom connection keeps working for everyone else on the team. If you disconnect Axiom in Elaichi, it is removed from Claude, ChatGPT, Cursor, and every other client in one step.
Does the Axiom MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Axiom is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Axiom?
Yes. Both let Claude, ChatGPT or Cursor use Axiom. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Axiom call.
How is Elaichi different from Composio for Axiom?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Axiom: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Axiom in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.