Skip to content

Control Plane MCP connector

The Control Plane connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client list, deploy, diagnose, restart, roll back and promote workloads across your GVCs and locations, as the signed-in person, with every call logged in Elaichi.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Diagnose the checkout workload in the production GVC

Working in Control Plane with Elaichi

  • Get cpln rules
  • Get cpln skill
  • Get resource schema
Ask anything…
Governance / Audit log Last 24 hours
Control Plane Get resource schema Emily Carter · ChatGPT · 9:41 AM Done
Control Plane Get cpln skill Emily Carter · ChatGPT · 9:41 AM Done
Control Plane Get cpln rules Emily Carter · ChatGPT · 9:41 AM Done
Control Plane Plan app Megan Brooks · Claude · 9:38 AM Done
Control Plane Get permissions Ryan Hayes · Cursor · 9:35 AM Done

How to connect Control Plane to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Control Plane MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

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

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Control Plane MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

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

Control Plane MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Control Plane MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Control Plane MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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 Control Plane to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Control Plane through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Control Plane is logged.

  • Platform

    Stand up a new environment for a team

    Describe the environment in plain words, and the agent creates the GVC, adds the locations it should run in, and deploys the first workload. The setup follows the Control Plane rules your organization already has in place.

  • Engineering

    Ship a build and confirm it landed

    Deploy an app to Control Plane from the chat you are already in, then ask whether the workload is healthy before telling the rest of the team.

  • On-call

    Diagnose a failing workload at 2am

    Ask what is wrong with a workload, restart it, or roll it back to the last good version without opening the Control Plane console. The agent only touches what your own Control Plane access allows.

  • Release management

    Promote a workload from staging to production

    Once a release has settled in staging, ask the agent to promote the workload and add a database if the new version needs one. Each step is written to the audit log with your name on it.

  • Security

    Review who and what can reach a resource

    Pull the permissions on any Control Plane resource, check which workloads are allowed to talk to each other, and grant cloud access only where it has been approved.

  • Developer experience

    Answer platform questions straight from the docs

    New engineers can search Control Plane documentation, rules and resource schemas in plain language, so the platform team stops answering the same question every week.

Try asking

  • “Diagnose the checkout workload in the production GVC”
  • “Roll back the api workload to the previous version”
  • “Add the aws-eu-central-1 location to the staging GVC”

See all 119 Control Plane tools →

What connecting Control Plane gets you

6 screens from Elaichi, each doing one job for your Control Plane account.

Elaichi Agent

Ask Elaichi to work across your apps.

Diagnose the checkout workload in the production GVC

Roll back the api workload to the previous version

Add the aws-eu-central-1 location to the staging GVC

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about your workloads in plain language.

Three starter prompts pull live answers from Control Plane workloads, GVCs and locations.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint connects Control Plane to every client.

Claude, ChatGPT, Cursor and Microsoft Copilot reach Control Plane through one governed endpoint, no SDK, no shared key.

ElaichiTools
Tool Action Description
Get cpln rules Get The operating guide: approval for high-impact actions, the platform facts the tools do not check, Terraform ownership, targets, CLI use, and failure handling. Optional, since the core rules arrive with every connection.
Get cpln skill Get The runbook for one task family: how to use a feature correctly, the constraints that are easy to miss, and when it's the wrong tool. Not advertised when the AI Plugin supplies its own skills.
Plan app Action Before any code for an app that keeps anything (content, records, files, or sign-ins): how Control Plane keeps its files, records, secrets, and replicas, and the tools that do each. The assistant settles what your request leaves open with you first. Not in `readonly`.
Get resource schema Get The exact object schema and REST endpoints for a resource kind, for authoring an accurate manifest or calling the API.
Get permissions Get The grantable permissions for a resource kind, for building policies.

Tool catalog

119 Control Plane tools, ready without code.

Workloads, GVCs, locations, databases and permissions, cataloged and callable with no custom code.

ElaichiToolboxes
Name Source template Tools Created

Platform toolbox

Control Plane · GVCs and locations

Control Plane starter 18 Mar 4, 2026

Engineering toolbox

Control Plane · workloads and deploys

— 9 Mar 2, 2026

On-call toolbox

Control Plane · diagnosis and rollbacks

— 24 Feb 27, 2026

Security toolbox

Control Plane · permissions and access

Control Plane starter 6 Feb 19, 2026

Data toolbox

Control Plane · databases and storage

— 31 Jan 30, 2026

Developer experience toolbox

Control Plane · docs and rules

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Control Plane toolbox.

Platform deploys and promotes, on-call diagnoses and restarts, each from a toolbox scoped to them.

ElaichiConnections
Connection Scope Status Access
CO

Control Plane (Platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
CO

Control Plane (Production)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
CO

Control Plane (Staging)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
CO

Control Plane (On-call)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
CO

Control Plane (Security)

Connected by Ryan Hayes

Personal • Active Not shared
CO

Control Plane (Data)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates deploy without ever holding a credential.

One person connects Control Plane, shares it with teams, and the sign-in stays with them.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Control Plane Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Control Plane Workloads Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Control Plane Workloads List Toolbox

Audit log

Every rollback is logged with a name.

When, who, what happened and which workload, kept in an append-only log.

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.

Control Plane digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch workloads

    Control Plane

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Control Plane

    Queued

Workflows

A schedule starts the work, a person approves.

Workload health is fetched, grouped and drafted into a digest, approved, then posted to Control Plane.

Control Plane health

Refreshed 4 minutes ago · every 15 minutes · from the workloads collection

Live

Workloads

1,284 ↓ 12%

Gvcs

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Workloads created

Last 14 days

By team

Share of activity

Platform 34%

Production 27%

Staging 21%

On-call 18%

Collections and dashboards

Workload health reported without asking anyone.

Four metrics and 14 days of workloads created, computed on a schedule with no model.

Why connect Control Plane's MCP server through Elaichi

Control Plane builds and runs this MCP server. Elaichi sits in front of it, so Control Plane's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Control Plane's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Control Plane's tools at the same Elaichi address as every other connected app. Nobody adds Control Plane's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Control Plane sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Control Plane's server. By default, a tool Control Plane does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Control Plane

    Control Plane builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Control Plane team.

    [email protected]

Why run a vendor's MCP server through Elaichi →

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Control Plane

All three can connect Control Plane to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Control Plane, by what to check
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 Control Plane tools Allow or restrict single Control Plane 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 Control Plane 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.

Control Plane tools for your AI agents

119 tools are ready to call through Elaichi's MCP endpoint the moment you connect Control Plane, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Control Plane builds and runs these tools.

Questions, answered

How do I connect Control Plane to Claude?

Two steps. In Elaichi, add the Control Plane connector and sign in to your Control Plane organization in the browser window that opens, approving the connection as yourself over OAuth. Then in Claude, open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate.

Does Control Plane work with ChatGPT and Cursor as well as Claude?

Yes. Once Control Plane 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 Control Plane once and every client you use picks it up.

What can an AI agent actually do with my Control Plane data?

With Control Plane connected, an agent can list and read your workloads, GVCs, locations and other resources, deploy an app, add a database, and diagnose, restart, roll back or promote a workload. It can also look up permissions, review which workloads can reach each other, and search Control Plane documentation and rules. Short, concrete asks such as "restart the checkout workload in production" work better than long sentences.

Does connecting Control Plane give the AI my whole organization?

No. Every call to Control Plane runs as the person who signed in, so the agent sees only the GVCs, workloads and resources that person can already see in Control Plane. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Control Plane itself allows.

Can my team share one Control Plane connection?

Yes. One person connects Control Plane in Elaichi and shares the connection with a team, and nobody else ever handles a credential or sees the sign-in. Each teammate still signs in to Elaichi as themselves, so the audit log records who deployed, restarted or rolled back which workload.

Can I stop an agent from deleting or changing things in Control Plane?

Yes. Restrictions in Elaichi apply per action, so you can allow reading and diagnosing Control Plane workloads while restricting deletes, rollbacks or changes to GVC locations. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.

What happens to a Control Plane connection when someone leaves?

Offboarding a person in Elaichi ends their access to Control Plane through every client at once. A Control Plane connection they shared keeps working for everyone else on the team. Disconnecting Control Plane once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.

Does the Control Plane MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Control Plane 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 Control Plane?

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

How is Elaichi different from Composio for Control Plane?

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

Put Control Plane 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