Maia MCP connector
The Maia connector brings Maia agents, tasks, allowlists, credentials, consumptions and custom connectors to Claude, ChatGPT, Cursor and Microsoft Copilot, so each person works in Maia as themselves with every call logged.
- App credentials
- Free 14-day trial
- No credit card
Which Maia agent tasks are still running from last night?
Working in Maia with Elaichi
-
List all Maia agents
-
Get single Maia agent by ID
-
List all Maia agents releases
How to connect Maia to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Maia 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.
Maia MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Maia 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. The plugin directory lives at chatgpt.com/plugins.
Maia 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.
Maia MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Maia 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.
What teams do with Maia through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Maia is logged.
-
Operations
Check on overnight sync tasks
Ask which Maia agent tasks are still running, which finished and which stopped, then get a plain summary before the morning standup instead of opening every agent one by one.
-
IT
Spin up a new Maia agent
Describe the agent you need, the credential it should use and the connection it runs against, and have it created in Maia with its first task queued, all from the chat you are already in.
-
Data
Stop a runaway task before it spreads
When a load is pushing bad rows, tell the agent to stop that Maia task and list anything else touching the same connection, then update the rest in bulk once the cause is fixed.
-
Security
Tighten an agent allowlist in bulk
Review the allowlist on a Maia agent, add the hosts a new partner needs and remove the ones that are no longer used, in one request rather than a dozen clicks.
-
Finance
Review consumption before the invoice lands
Pull this month's Maia consumptions and see which ETL users are driving them, so the bill is explained before anyone has to ask.
-
Platform
Approve a task decision from chat
When a Maia task is waiting on a human, see what it is asking, record the decision and let it continue, without leaving Claude or Cursor to find the right screen.
Try asking
- “Which Maia agent tasks are still running from last night?”
- “Summarize this month's Maia consumptions by ETL user.”
- “Create a Maia agent task to reconcile the Salesforce orders sync.”
What connecting Maia gets you
6 screens from Elaichi, each doing one job for your Maia account.
Ask Elaichi to work across your apps.
Which Maia agent tasks are still running from last night?
Summarize this month's Maia consumptions by ETL user.
Create a Maia agent task to reconcile the Salesforce orders sync.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Maia agents in plain language.
Get answers from live Maia agents, tasks and consumptions, no console required.
Copy the endpoint
AI apps
One endpoint puts Maia in every MCP client.
Claude, ChatGPT and Cursor reach Maia through one governed endpoint, no SDK, no shared key.
Tool catalog
113 Maia tools with no custom code.
Agents, tasks, allowlists, credentials and custom connectors, every resource and method cataloged for you.
Toolboxes
Every team gets its own Maia toolbox.
Scope Maia toolboxes to Operations, IT or Data so each team sees only its work.
Shared connections
Share Maia access without sharing a credential.
One person connects Maia, teammates work through it and never see the app credentials.
Audit log
Know who changed every Maia agent and task.
Every call shows when, who, what happened and which Maia resource it touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Maia digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch agents
Maia
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 Jake Morgan
Approve Deny -
Post the digest
Maia
Queued
Workflows
A schedule starts Maia work, a person approves.
Fetch Maia tasks nightly, group them, draft a digest, approve it, post it back.
Maia health
Refreshed 4 minutes ago · every 15 minutes · from the agents collection
Agents
1,284 ↓ 12%
Tasks
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Agents created
Last 14 days
By team
Share of activity
Operations 34%
IT 27%
Data 21%
Security 18%
Collections and dashboards
Maia health numbers arrive before anyone asks.
Agents, tasks and consumptions computed on a schedule, by team, with no model in the math.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Maia
All three can connect Maia 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 Maia tools | Allow or restrict single Maia 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 Maia 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 | Free for one person; $15 per user per month on Gold. | 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.
Maia tools for your AI agents
113 tools are ready to call through Elaichi's MCP endpoint the moment you connect Maia, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Maia to Claude?
Connect Maia in Elaichi first by entering your Maia app credentials once, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register in Maia and no client ID or secret to generate. After that Claude signs you in as yourself and you can start asking about agents and tasks.
Does Maia work with ChatGPT and Cursor as well as Claude?
Yes. Maia is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot or any other MCP client. The Elaichi Agent uses it too, so nobody sets Maia up a second time.
What can an AI agent actually do with my Maia data?
With Maia connected, an agent can list and create Maia agents, start, stop, update and delete their tasks, record task decisions, manage allowlists and credentials, and read consumptions, connection schemas and custom connectors. In practice that means asking what ran overnight, stopping a bad load or setting up a new agent in plain words. Short concrete asks like "stop the orders sync task" work better than long paragraphs.
Does connecting Maia give the AI every agent and credential in my workspace?
No. Every call into Maia runs as the person who signed in, so an agent can only reach the Maia agents, tasks and credentials that person could already reach. Elaichi can narrow that further with roles and restrictions, and it never widens it beyond what Maia itself allows.
Can I stop an agent from deleting or changing things in Maia?
Yes. Restrictions in Elaichi apply per action, so you can restrict deleting a Maia agent or deleting a task for a role or for one person while leaving reads open. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Maia connection when someone leaves?
Offboarding that person in Elaichi ends their access to Maia at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A Maia connection they shared keeps working for everyone else on the team. If you disconnect Maia once in Elaichi, it is removed from every client at the same time.
Does the Maia MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Maia 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, Microsoft Copilot, 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 Maia?
Yes. Both let Claude, ChatGPT or Cursor use Maia. 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 Maia call.
How is Elaichi different from Composio for Maia?
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 Maia: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Maia in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot