# Elastic Cloud MCP connector

The Elastic Cloud connector brings deployments, organization members, role assignments and API keys into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can review and manage them inside each person's own access.

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

## Facts

| | |
| --- | --- |
| Application | Elastic Cloud |
| Category | Application Development |
| AI tools | 108 |
| Authentication | Connects with an API key |
| 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 Elastic Cloud is connected

- List every API key in our Elastic Cloud organization created this month
- Which members hold admin role assignments in Elastic Cloud?
- Reset the APM secret token on the production deployment

## Connect Elastic Cloud in Elaichi

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

1. Open Connections, choose Add connection, and pick Elastic Cloud.
2. Optionally set Share with, then press Connect.
3. Paste an Elastic Cloud API key. One person generates a token in Elastic Cloud and pastes it once. Everyone else works through Share with, and never sees it.

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

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

## Elastic Cloud 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`.

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

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

## Elastic Cloud 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 Elastic Cloud 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 Elastic Cloud 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 Elastic Cloud through Elaichi

### Retire API keys nobody uses anymore

Platform. Ask for every API key in the Elastic Cloud organization, spot the ones created for a project that ended, and remove them in one pass.

### Run an access review before the audit

Security. Pull the full list of Elastic Cloud organization members and their role assignments, then confirm each person still needs what they have.

### Offboard an engineer the day they leave

IT. Remove the departing engineer from the Elastic Cloud organization and clear their role assignments without logging into the console.

### Rotate the APM secret token after an incident

SRE. Reset the APM secret token on the affected Elastic Cloud deployment and confirm the change before the postmortem is written.

### Check which clusters a deployment can reach

Engineering. Ask which remote clusters an Elastic Cloud deployment is eligible to connect to and read the deployment's certificate authority before wiring up cross cluster search.

### Put App Search into read only mode

Compliance. Switch App Search to read only during a freeze or a migration, and confirm the current mode on request without opening Elastic Cloud.

## Elaichi vs Zapier MCP vs Composio for Elastic Cloud

All three can connect Elastic Cloud 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 Elastic Cloud tools | Allow or restrict single Elastic Cloud 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 Elastic Cloud 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 Elastic Cloud to Claude?

Connect Elastic Cloud in Elaichi by pasting an Elastic Cloud API key when asked. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude signs you in through Elaichi and Elastic Cloud is available from the next conversation.

### Does Elastic Cloud work with ChatGPT and Cursor as well as Claude?

Yes. Once Elastic Cloud is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Elastic Cloud once and every client picks it up.

### What can an AI agent actually do with my Elastic Cloud data?

An agent can list the members of your Elastic Cloud organization, create or remove role assignments, create and delete API keys, and update organization details. It can also look at a deployment's APM and App Search resources, reset an APM secret token, set keystore values, read the certificate authority and check which remote clusters a deployment can connect to. Short, concrete asks such as list every API key created this month work better than long sentences.

### Does connecting Elastic Cloud give the AI access to my whole organization?

No. Every call to Elastic Cloud runs with the access of the person who signed in, so an agent can only see the organizations, deployments and keys that person can already see. Elaichi can narrow that further with roles and restrictions, and it never widens it beyond what Elastic Cloud already allows.

### Can my team share one Elastic Cloud connection?

Yes. One person connects Elastic Cloud in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every action on Elastic Cloud is logged under their own name.

### Can I stop an agent from deleting or changing things in Elastic Cloud?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Elastic Cloud members and keys while restricting deleting a member, removing an API key or changing a keystore. A restriction is set on a role or on one person, the restricted action still shows in Elaichi's tool search flagged as restricted, and no client can run it whatever the prompt says.

### What happens to an Elastic Cloud connection when someone leaves?

Offboarding a person in Elaichi ends their access to Elastic Cloud through every client at once. A shared Elastic Cloud connection keeps working for everyone else on the team. If you disconnect Elastic Cloud in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent in one step.

### Does the Elastic Cloud MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Elastic Cloud 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 Elastic Cloud?

Yes. Both let Claude, ChatGPT or Cursor use Elastic Cloud. 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 Elastic Cloud call.

### How is Elaichi different from Composio for Elastic Cloud?

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 Elastic Cloud: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 108 Elastic Cloud tools

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

- **List all Elastic Cloud organization members** (List). Fetch users belonging to the selected organization. Currently unavailable in self-hosted ECE. Required: organization_id.
- **Delete a Elastic Cloud organization member by ID** (Delete). Deletes one or more organization memberships. Currently unavailable in self-hosted ECE. Required: id, organization_id. id is the user_ids (comma-separated).
- **List all Elastic Cloud organizations** (List). Fetch organizations available to the current user. Currently unavailable in self-hosted ECE.
- **Get single Elastic Cloud organization by ID** (Get). Fetch a single organization by id. Currently unavailable in self-hosted ECE. Required: id. id is the organization_id.
- **Update a Elastic Cloud organization by ID** (Update). &gt; WARNING &gt; This endpoint is deprecated and scheduled to be removed in the next major version. Updates an existing organization. Currently unavailable in self-hosted ECE. Body fields: name, enforce_authentication_method, default_disk_usage_alerts_enabled, notifications_allowed_email_domains, billing_contacts, operational_contacts. Required: id. id is the organization_id.
- **List all Elastic Cloud myaccount** (List). Fetch current account information.
- **Elastic Cloud myaccount patch** (Action). Updates the current account. Body fields: trust.
- **Elastic Cloud myaccount replace** (Action). Updates the current account. Body fields: trust.
- **Create a Elastic Cloud role assignment** (Create). Adds a set of RoleAssignments to the specified User. Currently unavailable in self-hosted ECE. Body fields: platform, organization, deployment, project. Required: user_id.
- **Delete a Elastic Cloud role assignment by ID** (Delete). Removes a set of RoleAssignments from the specified User. Currently unavailable in self-hosted ECE. Body fields: platform, organization, deployment, project. Required: user_id.
- **Create a Elastic Cloud API key** (Create). Creates a new API key. The key value is only returned once, in this response. Body fields: description, expiration, role_assignments. Required: description.
- **Delete a Elastic Cloud API key by ID** (Delete). Delete or invalidate the API key. Required: id. id is the api_key_id.
- **Elastic Cloud API keys delete many** (Delete). Delete or invalidate API keys. Body fields: keys. Required: keys.
- **Get single Elastic Cloud API key by ID** (Get). Retrieves the metadata for an API key. Required: id. id is the api_key_id.
- **List all Elastic Cloud API keys** (List). Retrieves the metadata for the API keys the caller is allowed to see.
- **List all Elastic Cloud appsearch read only mode** (List). Enable/Disable read-only mode on the given App Search resource. Required: deployment_id, ref_id.
- **Elastic Cloud appsearch read only mode set** (Set). Enable/Disable read-only mode on the given App Search resource. Body fields: enabled. Required: deployment_id, ref_id, enabled.
- **List all Elastic Cloud deployment apm resources** (List). Get info about an APM Resource belonging to a given Deployment. Required: deployment_id, ref_id.
- **Elastic Cloud deployment apm resources reset secret token** (Action). Reset the token of an APM resource. Returns the new secret token. Required: deployment_id, ref_id.
- **List all Elastic Cloud deployment appsearch resources** (List). Get info about an App Search Resource belonging to a given Deployment. Required: deployment_id, ref_id.
- **List all Elastic Cloud deployment certificate authority** (List). Returns the certificate authority used to sign the certificates of this deployment. Required: deployment_id.
- **Deployment elasticsearch eligible remote clusters search** (Search). Returns the list of deployments which contain eligible remote clusters for the elasticsearch resource. Body fields: from, cursor, size, query, sort. Required: deployment_id, ref_id.
- **List all Elastic Cloud deployment elasticsearch keystore** (List). Fetches the current fields and metadata (but not the values) of the keystore for the Elasticsearch resource. Required: deployment_id, ref_id.
- **Elastic Cloud deployment elasticsearch keystore set** (Set). Adds the specified values to the Elasticsearch keystore, or removes the keys for the unspecified values. Body fields: secrets. Required: deployment_id, ref_id, secrets.
- **List all Elastic Cloud deployment elasticsearch remote clusters** (List). Returns the list of certificate based remote clusters for the elasticsearch resource. Required: deployment_id, ref_id.
- **Elastic Cloud deployment elasticsearch remote clusters set** (Set). Overwrites or creates the list of certificate based remote clusters for the elasticsearch resource. Body fields: resources. Required: deployment_id, ref_id, resources.
- **Elastic Cloud deployment elasticsearch resources enable ccr** (Enable). Migrates the specified Elasticsearch resource and its associated Kibana to enable CCR (if supported). Required: deployment_id, ref_id.
- **Elastic Cloud deployment elasticsearch resources enable ilm** (Enable). Migrates the specified Elasticsearch resource to use ILM. Body fields: index_patterns. Required: deployment_id, ref_id, index_patterns.
- **Elastic Cloud deployment elasticsearch resources enable slm** (Enable). Migrates the specified Elasticsearch resource to use SLM. Required: deployment_id, ref_id.
- **List all Elastic Cloud deployment elasticsearch resources** (List). Get info about an Elasticsearch Resource belonging to a given Deployment. Required: deployment_id, ref_id.
- **Elastic Cloud deployment elasticsearch resources reset password** (Action). Resets the password of the 'elastic' user. Returns the new elastic user password in the response. Required: deployment_id, ref_id.
- **Elastic Cloud deployment elasticsearch resources restart** (Restart). Restarts an Elasticsearch Resource. If a Resource is active: this command re-applies the existing plan but applies a "cluster_reboot", which issues a restart command and waits for it to complete. If a Resource is inactive: this command starts it up with the most recent successful plan. Required: deployment_id, ref_id.
- **Elastic Cloud deployment elasticsearch resources shutdown** (Action). Shutdown Elasticsearch Resource belonging to a given Deployment. Required: deployment_id, ref_id.
- **Create deployment elasticsearch snapshot repository** (Create). Important: This API is currently in Tech Preview. While available for use, it is subject to change. Creates a snapshot dependency, allowing this cluster to access snapshots from the source deployment. Currently unavailable in self-hosted ECE. Body fields: source_deployment_id. Required: deployment_id, ref_id, source_deployment_id.
- **Delete deployment elasticsearch snapshot repository by ID** (Delete). Removes the attached snapshot repository. This is only possible if the repository is not in use anymore by any searchable snapshots. Required: id, deployment_id, ref_id. id is the repository_name.
- **List all deployment elasticsearch snapshot repositories** (List). Lists all the snapshot repositories this deployment has access to. These are snapshot repositories of other deployments that have been linked to this deployment. Required: deployment_id, ref_id.
- **List all Elastic Cloud deployment elasticsearch tiers** (List). Retrieves the current memory size, zone count, and available sizes for all enabled Elasticsearch tiers in a Deployment. Disabled tiers are excluded. Required: deployment_id, ref_id.
- **Elastic Cloud deployment elasticsearch tiers patch** (Action). Updates the size and/or zone count of one or more Elasticsearch topology elements (tiers) within a Deployment. Body fields: hot_content, warm, cold, frozen, master, coordinating, ml. Required: deployment_id, ref_id.
- **List all Elastic Cloud deployment enterprise search resources** (List). Get info about an Enterprise Search Resource belonging to a given Deployment. Required: deployment_id, ref_id.
- **List all Elastic Cloud deployment integrations server resources** (List). Get info about an Integrations Server Resource belonging to a given Deployment. Required: deployment_id, ref_id.
- **List all Elastic Cloud deployment kibana resources** (List). Get info about a Kibana Resource belonging to a given Deployment. Required: deployment_id, ref_id.
- **List all Elastic Cloud deployment resource user settings** (List). Retrieves the current user-defined settings for a resource belonging to a given Deployment. Required: deployment_id, resource_kind, ref_id.
- **Elastic Cloud deployment resource user settings set** (Set). Replaces the component-level user-defined settings for the specified resource kind in the deployment. All existing component-level user settings are overwritten with the provided values. Submitting an empty object will remove all component-level user settings for the resource. This endpoint does not support tier/topology-level user settings overrides. Body fields: user_settings. Required: deployment_id, resource_kind, ref_id, user_settings.
- **Elastic Cloud deployment resources cancel pending plan** (Cancel). Cancels the pending plan of a Resource belonging to a given Deployment. Required: deployment_id, resource_kind, ref_id.
- **Elastic Cloud deployment resources restart stateless** (Restart). Restarts a Stateless Resource. If a Resource is active: this command re-applies the existing plan but applies a "cluster_reboot", which issues a restart command and waits for it to complete. If a Resource is inactive: this command starts it up with the most recent successful plan. Required: deployment_id, stateless_resource_kind, ref_id.
- **Elastic Cloud deployment resources restore** (Restore). Restores a shutdown resource belonging to a given Deployment. Required: deployment_id, resource_kind, ref_id.
- **Elastic Cloud deployment resources shutdown stateless** (Action). Shut down Stateless Resource belonging to a given Deployment. Kibana cannot be shut down on Elasticsearch Service as it is required for Elasticsearch administrative functions, such as Snapshot Lifecycle Management and version upgrades. Required: deployment_id, stateless_resource_kind, ref_id.
- **Elastic Cloud deployment resources start all instances** (Start). Starts all instances belonging to a Deployment Resource. Required: deployment_id, resource_kind, ref_id.
- **Elastic Cloud deployment resources start all maintenance mode** (Start). Starts maintenance mode of all instances belonging to a Deployment Resource. Required: deployment_id, resource_kind, ref_id.
- **Elastic Cloud deployment resources start instances** (Start). Starts instances belonging to a Deployment Resource. Required: deployment_id, resource_kind, ref_id, instance_ids.
- ...and 58 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
