# 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.

Source: https://elaichi.ai/connectors/maia/

## Facts

| | |
| --- | --- |
| Application | Maia |
| Category | IPAAS |
| AI tools | 113 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Maia is connected

- 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.

## Connect Maia in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Maia.
2. Optionally set Share with, then press Connect.
3. Paste your Maia app credentials. Maia authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Maia tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Maia MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Maia MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Maia tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Maia through Elaichi

### Check on overnight sync tasks

Operations. 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.

### Spin up a new Maia agent

IT. 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.

### Stop a runaway task before it spreads

Data. 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.

### Tighten an agent allowlist in bulk

Security. 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.

### Review consumption before the invoice lands

Finance. Pull this month's Maia consumptions and see which ETL users are driving them, so the bill is explained before anyone has to ask.

### Approve a task decision from chat

Platform. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Maia connection?

Yes. One person connects Maia in Elaichi and shares the connection with a team, and nobody else ever handles the Maia app credentials. Each teammate still signs in as themselves, so the audit log names the actual person who created an agent or stopped a task.

### 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.

## All 113 Maia tools

Every tool below is callable through https://api.elaichi.ai/mcp once Maia is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Maia agents** (List). List all Maia runners (agents), including summary details for each. Returns: agentId, agentStatus, agentType, cloudProvider, connected, deployment, description, name, pausedUntil, enableAutoUpdates, restrictedAccess, versionDetails. Max 100 per page.
- **Create a Maia agent** (Create). Create a new Maia runner (agent) with the specified configuration. Returns: agentId, agentStatus, agentType, cloudProvider, connected, deployment, description, enableAutoUpdates, name, pausedUntil, versionDetails, and 1 more. Required: name, agentType, cloudProvider, deployment. An agentType of 'streaming' cannot have enableAutoUpdates set to true.
- **Get single Maia agent by ID** (Get). Get details for a specific Maia runner (agent) by id. Returns: agentId, agentStatus, agentType, cloudProvider, connected, deployment, description, enableAutoUpdates, name, pausedUntil, restrictedAccess, versionDetails. Required: id.
- **Update a Maia agent by ID** (Update). Update a Runner in Maia. Returns an empty 202 response on success. All body fields are optional: name, description, enableAutoUpdates, restrictedAccess, trackName (CURRENT or STABLE). Snowflake runners cannot be updated and enableAutoUpdates cannot be set for them. Required: id.
- **Delete a Maia agent by ID** (Delete). Delete a Runner in Maia by id. Returns an empty 202 response on success. Only runners with a STOPPED, PENDING or UNKNOWN status can be deleted; UNKNOWN-status runners have up to a one-hour delay before deletion succeeds. Required: id.
- **List all Maia agents releases** (List). List runner version track history entries in Maia. Returns a paginated list with: trackName, version, supportLevel, releasedAt. Filterable by track, support level, version, or release date range. Max 100 per page.
- **Get single Maia agent allowlist by ID** (Get). Get the allow list of projects a Maia runner is restricted to, by runner id. Returns a map of project IDs to entries with their allowed environments; an empty map means the runner can be assigned to no project while restrictedAccess is true. Required: id.
- **Maia agent allowlists bulk update** (Update). Replace a Maia runner's entire allow list with the supplied projects and environments, overwriting any previously set values; send an empty projects object to clear the list. Returns an empty 202 response on success. Required: agent_id, projects.
- **Maia agent allowlists bulk add** (Add). Add projects and/or environments to a Maia runner's allow list without removing existing entries. Returns an empty 202 response on success. Required: agent_id, projects.
- **Maia agent allowlists bulk delete** (Delete). Remove a project, or a single environment within a project, from a Maia runner's allow list. Omitting environmentName removes the entire project and its environments. Returns an empty 202 response on success. Required: agent_id, projectId.
- **Create a Maia agent command** (Create). Trigger a Runner command in Maia — RESTART restarts the runner, PAUSE sets it to 'Paused', and RESUME un-pauses it. Returns an empty 202 response on success. Required: agent_id, command.
- **List all Maia agent credentials** (List). Get the client credentials for a Maia Runner agent. Returns the AgentCredentials record with clientId (the Runner's Client ID) and clientSecret (the Runner's Client secret). Required: agent_id. Returns 400 for wrong request parameters, 403 when access is forbidden, and 404 when the runner does not exist.
- **Create a Maia agent credential** (Create). Refresh the client credentials of a Maia Runner agent by POSTing a SECRET_REFRESH action. Returns the refreshed AgentCredentials record with clientId (the Runner's Client ID) and clientSecret (the Runner's Client secret). Required: agent_id, action. Returns 400 for wrong request parameters, 403 when access is forbidden, and 404 when the runner…
- **List all Maia agents tasks** (List). List AI agent tasks in Maia, optionally filtered by project, branch, status, or creation time. Returns tasks with taskId, status, agentName, mode, description, createdAt, and modifiedAt, plus the total count.
- **Create a Maia agents task** (Create). Create a Maia AI agent task and start its async execution. Returns: agentName, createdAt, status, taskId. Required: message, agentConfig.
- **Get single Maia agents task by ID** (Get). Get a single Maia AI agent task by id, including its current status and pending decisions. Returns: agentConfig, createdAt, description, grantedPermissions, modifiedAt, pendingDecisions, status, taskId. Required: id.
- **Delete a Maia agents task by ID** (Delete). Delete an AI agent task in Maia by id. The task must not be in RUNNING status. Returns an empty 204 response on success. Required: id.
- **Maia agents tasks stop** (Stop). Stop a running AI agent task in Maia; the task finishes its current work before stopping. Returns an empty 204 response on success. Only tasks in a running state can be stopped; poll the task status until it reaches STOPPED before further operations. Required: task_id.
- **Maia agents tasks bulk update** (Update). Replace the full set of granted tool permissions for a Maia AI agent task; pass an empty grantedPermissions list to clear all permissions. Returns: grantedPermissions, taskId. Required: task_id, grantedPermissions.
- **Create a Maia task decision** (Create). Submit approval or question-answer decisions for a Maia AI agent task that is awaiting human input. Returns the processing result including pendingDecisions. Required: task_id, decisions.
- **List all Maia connections schemas** (List). Get the Maia connection schema describing the connection properties and vault secret format required to create a connection. Returns: authProvider, authType, connectionPropertiesFields, platformConnectionType, vaultSecretFormat. Required: authProvider, authType, platformConnectionType.
- **List all Maia consumptions** (List). Get a breakdown of credit consumption in Maia for flat-rated products, grouped by calendar day (UTC) and by consumption type. Returns: consumedBefore, consumedFrom, consumption. Required: consumedFrom, consumedBefore. Data refreshes every three hours.
- **List all Maia consumption etl users** (List). Get a breakdown of maia credit consumption for ETL Users over a period. Returns: chargedUsers, consumedBefore, consumedFrom, credits. Required: consumedFrom, consumedBefore.
- **List all Maia custom connectors** (List). List the custom connector profiles configured for your Maia account, which can be used to create resources where required.
- **List all Maia flex connectors** (List). List Maia flex connector profiles that can be used to create resources where required. Returns: name, icon, logo, endpoints, deleted, deletedTime, lastModified.
- **List all Maia SCIM groups** (List). Search Maia SCIM Groups with filtering, sorting, and pagination. Returns each matching group's id and its schema-specific attributes. Max 100 per page.
- **Create a Maia SCIM group** (Create). Create a new SCIM Group in Maia for directory-integration user/group permission management. Returns: accountId, accountName, displayName, environment, externalId, id, members, meta, projectId, projectName, role, schemas. Required: meta.
- **Get single Maia SCIM group by ID** (Get). Get a single SCIM Group in Maia by id. Returns: accountId, accountName, displayName, environment, externalId, id, members, meta, projectId, projectName, role, schemas. Required: id.
- **Update a Maia SCIM group by ID** (Update). Update a SCIM Group in Maia by id. Returns: accountId, accountName, displayName, environment, externalId, id, members, meta, projectId, projectName, role, schemas. Required: id, meta.
- **Delete a Maia SCIM group by ID** (Delete). Delete a Maia SCIM Group by its unique id. Returns an empty 204 response on success. Required: id.
- **Maia SCIM groups partial update** (Update). Update a SCIM group in Maia by sending a SCIM patch Operations array. Returns the updated group including id, displayName, members, role, accountId, and schemas. Required: group_id.
- **List all Maia SCIM resource types** (List). List all SCIM resource types Maia supports for directory-integration user and group permission management. Returns resource type records with id and their SCIM-defined attributes.
- **List all Maia SCIM schemas** (List). List all supported SCIM schemas in Maia's directory integration. Returns each schema definition's id plus its schema-specific attributes; the attribute fields are not enumerated in the API reference and vary per SCIM schema.
- **List all Maia SCIM service provider configs** (List). Get the SCIM Service Provider Configuration in Maia, describing the SCIM service provider's supported features and configuration. Returns the Service Provider Configuration object with SCIM-defined fields; the published spec models the response as an open object without an enumerated field list.
- **List all Maia SCIM users** (List). Search SCIM users in Maia with filtering and sorting. Returns: id, attributes. Max 100 per page.
- **Create a Maia SCIM user** (Create). Create a new SCIM User in Maia to manage directory-based permissions. Returns the created user with id, userName, displayName, emails, active, and meta. Requires a SCIM user payload (meta required). Required: meta.
- **Get single Maia SCIM user by ID** (Get). Get a SCIM User by id in Maia. Returns the user including id, userName, displayName, emails, active, and meta. Required: id.
- **Update a Maia SCIM user by ID** (Update). Update a SCIM User by id in Maia. Returns the updated user with id, userName, displayName, emails, active, and meta. Required: id, meta.
- **Delete a Maia SCIM user by ID** (Delete). Delete a SCIM user in Maia by id. Returns an empty 204 response on success. Required: id.
- **Maia SCIM users partial update** (Update). Patch a SCIM user in Maia's directory integration by applying SCIM PatchOp Operations to update user attributes. Returns the updated user object with id, userName, displayName, active, emails, groups, and meta. Required: user_id.
- **List all Maia events** (List). Query Maia audit events within a time range. Returns each event's eventId, eventName, eventType, actorEmail, and eventTimestamp. Required: from, to.
- **List all Maia lineage events** (List). List OpenLineage lineage events in chronological order within a date range. Returns: id, event. Max 100 per page (default 100). Required: generatedFrom, generatedBefore.
- **List all Maia pipeline executions** (List). List summarised pipeline executions in Maia, ordered by most recent start time. Returns: environmentName, finishedAt, message, pipelineExecutionId, pipelineName, pipelineType, projectId, scheduleId, startedAt, status, trigger, user. Max 100 per page.
- **Create a Maia project pipeline execution** (Create). Execute a published pipeline in a Maia project. Runs asynchronously and returns pipelineExecutionId for tracking the run. Only one execution per executionTag may run at a time (409 Conflict otherwise). Required: project_id, environmentName, pipelineName. Pipeline names must include the file extension, for example my_pipeline.orch.yaml or my_pipeline.tran.yaml.
- **Get single Maia project pipeline execution by ID** (Get). Get the details of a pipeline execution in a Maia project by id, including its current status, trigger, timings, and result message. Returns: environmentName, finishedAt, message, pipelineExecutionId, pipelineName, pipelineType, projectId, scheduleId, startedAt, status, trigger, user. Required: id, project_id.
- **Update a Maia project pipeline execution by ID** (Update). Cancel a running pipeline execution in a Maia project by id, optionally forcing hard termination. Returns pipelineExecutionId on success. Required: id, project_id, forceUpdate, status.
- **Get single Maia pipeline execution status by ID** (Get). Get the current status of a pipeline execution in Maia. Returns: status. Required: id, project_id.
- **List all Maia pipeline execution steps** (List). List the step statuses of a pipeline execution in Maia. Returns each step's id, name, childPipeline, and result. Max 100 per page. Required: project_id, pipeline_execution_id.
- **List all Maia pipeline execution tasks** (List). List the tasks of a maia pipeline execution as a flat, paged list covering the root execution and every child execution beneath it. Returns: pipeline, task. Max 100 per page. Required: project_id, pipeline_execution_id.
- **List all Maia projects** (List). List all projects in Maia. Returns: description, id, name. Max 100 records per page.
- ...and 63 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
