DoiT MCP connector
The DoiT connector brings DoiT cloud cost alerts, allocations, annotations, and labels to Claude, ChatGPT, Cursor, and any MCP client, so your team can ask about and manage them in plain language inside their own DoiT access.
-
How it connects. Connects with an API key. 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.
How to connect
How to connect DoiT to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect DoiT once
-
Open Connections, choose Add connection, and pick DoiT.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a DoiT API key. One person generates a token in DoiT and pastes it once. Everyone else works through Share with, and never sees it.
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.
DoiT 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.
DoiT 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.
DoiT 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 DoiT 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 DoiT through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
FinOps
Set up a cost alert without the console
Ask for a new DoiT alert on a budget line or a spend spike, or adjust the threshold on an existing one, straight from the chat window. The alert is created in DoiT under your own access.
-
Finance
Review how cloud spend is allocated
List every DoiT allocation, ask what each one covers, and tidy up rules that no longer match how cost centers are organized. Update or retire an allocation as teams change.
-
Engineering
Note why the bill moved
After a migration or a big deploy, add a DoiT annotation so anyone looking at the cost chart later sees what happened and when.
-
Platform
Keep labels tidy across accounts
See which DoiT labels exist, create new ones for a product line or environment, and assign them so reports group the right resources together.
-
Leadership
Check which alerts are watching spend
Ask which DoiT alerts are active, what each one triggers on, and whether a new product or region has any coverage at all, without opening the console.
-
Operations
Clean up stale alerts and allocations
Pull the full list of DoiT alerts and allocations, spot the ones tied to projects that have ended, and remove them once the owner has confirmed.
Try asking
- “List DoiT analytics alerts created this month.”
- “Summarize spend by DoiT allocation for last quarter.”
- “Add an annotation to the DoiT cost report.”
Compare
Elaichi vs Zapier MCP vs Composio for DoiT
All three can connect DoiT 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 DoiT tools | Allow or restrict single DoiT 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 DoiT 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
DoiT tools for your AI agents
129 tools are ready to call through Elaichi's MCP endpoint the moment you connect DoiT, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting DoiT gets you
6 screens from the product, each doing one job for your DoiT account.
The agent
Ask about DoiT alerts, get real answers.
Plain language questions run against live DoiT alerts, allocations and annotations.
- alerts
- allocations
- annotations
- reports
Ask Elaichi to work across your apps.
List DoiT analytics alerts created this month.
Summarize spend by DoiT allocation for last quarter.
Add an annotation to the DoiT cost report.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach DoiT here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
129 DoiT tools, no custom code.
Alerts, allocations and annotations covered across list, create, update and delete methods.
- List all DoiT analytics alerts
- Create a DoiT analytics alert
- Get single DoiT analytics alert by ID
- Update a DoiT analytics alert by ID
Toolboxes
Every team gets its own DoiT toolbox.
Finance, platform and data teams each see a toolbox scoped to them.
- Finance
- Cloud platform
- Data
- Engineering leadership
Shared connections
Teammates use DoiT without touching credentials.
Each connection shows who added the DoiT account and which teams share it.
- Finance EMEA
- Cloud platform
- Data team
- FinOps
Audit log
Every DoiT call is on the record.
When, who, what happened, type and resource for each alert or allocation touched.
- When
- Who
- What happened
- Type
Launching 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 your DoiT cost digest.
Six steps fetch DoiT allocations, group them, draft a digest, then post on approval.
DoiT digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch alerts
DoiT
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
DoiT
Queued
Collections and dashboards
DoiT numbers land before anyone asks.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
DoiT health
Refreshed 4 minutes ago · every 15 minutes · from the alerts collection
Alerts
1,284 ↓ 12%
Allocations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Alerts created
Last 14 days
By team
Share of activity
Finance EMEA 34%
Cloud platform 27%
Data team 21%
FinOps 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect DoiT to Claude?
Two steps. In Elaichi, open the DoiT connector and paste in a DoiT API key, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register in DoiT and no client ID or secret to generate; the API key is the whole sign-in step. Once it is connected, Claude signs in through Elaichi as you and works inside your own DoiT access.
Does DoiT work with ChatGPT and Cursor as well as Claude?
Yes. DoiT is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is what Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent connect to. You do not set DoiT up again for each client.
What can an AI agent actually do with my DoiT data?
With DoiT connected, an agent can list your cost alerts and tell you what each one watches, create or update an alert, review and change how spend is allocated, add annotations to explain a change in the bill, and create and assign labels so reports group the right things. It can also list and create settings themes. Short, concrete asks such as "list active DoiT alerts" work better than a long paragraph, because the agent looks up the right action from a large set.
Does connecting DoiT give the AI everything in my DoiT account?
No. Every call to DoiT runs as the person who signed in, so the agent sees the alerts, allocations, annotations, and labels that person can already see in DoiT, and nothing more. Elaichi can narrow that further, for example to reading only, but it can never widen access beyond what your DoiT account allows.
Can I stop an agent from deleting or changing things in DoiT?
Yes. Restrictions in Elaichi work per action, so you can allow reading DoiT alerts and allocations while blocking the ability to delete or update them. A blocked action is never shown to Claude, ChatGPT, or Cursor at all, so no prompt, however worded, can reach it.
What happens to a DoiT connection when someone leaves?
Offboarding that person in Elaichi ends their access to DoiT through every AI client at once. If they were using a shared DoiT connection, it keeps working for everyone else on the team. If you want DoiT gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Does the DoiT MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. DoiT 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 DoiT?
Yes. Both let Claude, ChatGPT or Cursor use DoiT. 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 DoiT call.
How is Elaichi different from Composio for DoiT?
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 DoiT: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put DoiT 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.