Skip to content

Feature Flag

ConfigCat MCP connector

The ConfigCat connector brings feature flag settings, configs, environments, segments and change requests into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can read and update them inside each person's own ConfigCat access, with every call logged.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Which ConfigCat change requests are still waiting for approval?

Working in ConfigCat with Elaichi

  • Get single ConfigCat change request by ID
  • Get single ConfigCat proxy profile by ID
  • List all ConfigCat product change requests
Ask anything…
Governance / Audit log Last 24 hours
ConfigCat List all ConfigCat product change requests Emily Carter · ChatGPT · 9:41 AM Done
ConfigCat Get single ConfigCat proxy profile by ID Emily Carter · ChatGPT · 9:41 AM Done
ConfigCat Get single ConfigCat change request by ID Emily Carter · ChatGPT · 9:41 AM Done
ConfigCat Update a ConfigCat change request by ID Megan Brooks · Claude · 9:38 AM Done
ConfigCat ConfigCat change requests approve Ryan Hayes · Cursor · 9:35 AM Done

How to connect ConfigCat to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

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

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

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

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

ConfigCat 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 ConfigCat 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 ConfigCat through Elaichi

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

  • Engineering

    Clear the change request queue

    List the ConfigCat change requests still waiting on a product, read what each one proposes, and approve the ones that are ready without opening a browser tab for each.

  • Product

    See every flag in a config

    Ask for all the settings in a ConfigCat config and get a plain list of what is live, so a product review starts from the real state rather than a stale spreadsheet.

  • QA

    Stand up a new test environment

    Create a fresh ConfigCat environment for a release candidate, then check which configs and settings it carries before the test run starts.

  • Platform

    Keep proxy profiles up to date

    Pull up a ConfigCat proxy profile by name, update the parts that changed, and retire the profiles nobody uses anymore.

  • Customer success

    Build a segment for a beta cohort

    Create a ConfigCat segment for the customers who asked for early access, so the engineering team can target a flag at exactly those accounts.

  • Release management

    Map products, configs and environments

    List every ConfigCat product in the organization with its configs and environments, and spot the ones that are missing a staging or production environment.

Try asking

  • “Which ConfigCat change requests are still waiting for approval?”
  • “List every setting in the Mobile App production config.”
  • “Create a Beta customers segment in the Checkout product.”

See all 124 ConfigCat tools →

What connecting ConfigCat gets you

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

Elaichi Agent

Ask Elaichi to work across your apps.

Which ConfigCat change requests are still waiting for approval?

List every setting in the Mobile App production config.

Create a Beta customers segment in the Checkout product.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about any feature flag in plain language.

Get answers from live ConfigCat configs, environments and change requests, no dashboard digging.

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 ConfigCat endpoint for every MCP client.

Claude, ChatGPT, Cursor and Microsoft Copilot share one governed endpoint, no SDK and no shared API key.

ElaichiTools
Tool Action Description
Get single ConfigCat change request by ID Get Get the details of a specific ConfigCat Change Request by id. Returns: title, reason, createdAt, comments, approved, approvals, activities, id, created_at, updated_at. Required: id.
Update a ConfigCat change request by ID Update Update the metadata of a ConfigCat Change Request by id, such as its title, note, or schedule. Returns: title, reason, createdAt, comments, approved, approvals, activities, id, created_at, updated_at. Required: id, title.
ConfigCat change requests approve Approve Add your approval to a ConfigCat Change Request. Returns: title, reason, createdAt, comments, approved, approvals, activities, id, created_at, updated_at. Required: change_request_id.
Get single ConfigCat proxy profile by ID Get Get a single ConfigCat Proxy Profile by id. Returns the profile including proxyProfileId, name, description, lastAccessedAt, connectionPreferences, and sdkKeySelectionRules. Required: id.
Update a ConfigCat proxy profile by ID Update Replace a ConfigCat Proxy Profile by id with a complete body; any attribute omitted from the request is reset. Returns the updated profile including proxyProfileId, name, description, connectionPreferences, and sdkKeySelectionRules. Required: id, name.

Tool catalog

124 ConfigCat tools, ready without writing code.

Settings, configs, environments, segments, products and change requests covered, no custom code required.

ElaichiToolboxes
Name Source template Tools Created

Engineering toolbox

ConfigCat · configs and settings

ConfigCat starter 18 Mar 4, 2026

Product toolbox

ConfigCat · flags and rollouts

— 9 Mar 2, 2026

QA toolbox

ConfigCat · test environments

— 24 Feb 27, 2026

Platform toolbox

ConfigCat · proxy profiles and products

ConfigCat starter 6 Feb 19, 2026

Customer success toolbox

ConfigCat · segments and cohorts

— 31 Jan 30, 2026

Release management toolbox

ConfigCat · change requests and approvals

— 12 Jan 22, 2026

Toolboxes

Every team gets its own ConfigCat toolbox.

Scope what Engineering, Product and QA can reach in ConfigCat, team by team.

ElaichiConnections
Connection Scope Status Access
CO

ConfigCat (Engineering)

Connected by Emily Carter

Personal • Active 1 team · 6 members
CO

ConfigCat (Product)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
CO

ConfigCat (QA)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
CO

ConfigCat (Platform)

Connected by Tyler Reed

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

ConfigCat (Customer success)

Connected by Ryan Hayes

Personal • Active Not shared
CO

ConfigCat (Release)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share one ConfigCat connection, never the key.

Teammates work through the connection while the API key stays with whoever connected it.

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]

ConfigCat Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

ConfigCat Configs Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

ConfigCat Configs List Toolbox

Audit log

Know who changed which flag, and when.

Every ConfigCat call lands in an append-only log with actor, action, type and resource.

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.

ConfigCat digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch configs

    ConfigCat

    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

    ConfigCat

    Queued

Workflows

A schedule turns pending change requests into action.

Pending ConfigCat change requests are fetched, grouped, drafted into a digest, approved, then posted back.

ConfigCat health

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

Live

Configs

1,284 ↓ 12%

Environments

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Configs created

Last 14 days

By team

Share of activity

Engineering 34%

Product 27%

QA 21%

Platform 18%

Collections and dashboards

ConfigCat health, computed on a schedule, no model.

Four metrics, a 14 day chart of settings created, and a breakdown by team.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for ConfigCat

All three can connect ConfigCat 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 ConfigCat, 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 ConfigCat tools Allow or restrict single ConfigCat 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 ConfigCat 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.

ConfigCat tools for your AI agents

124 tools are ready to call through Elaichi's MCP endpoint the moment you connect ConfigCat, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect ConfigCat to Claude?

Connect ConfigCat in Elaichi first, which asks for a ConfigCat API key and nothing else, so 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 your ConfigCat products, configs and change requests are available from the next conversation.

Does ConfigCat work with ChatGPT and Cursor as well as Claude?

Yes. Once ConfigCat 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 ConfigCat once and every client picks it up.

What can an AI agent actually do with my ConfigCat data?

An agent can list your ConfigCat products, configs, environments and segments, show every setting in a config, and pull up a single change request or proxy profile by ID. It can also create environments, configs and segments, update or approve change requests, and update or delete proxy profiles and products. Short concrete asks, like naming the product and environment you mean, get better results than long sentences.

Does connecting ConfigCat give the AI access to every product and environment?

No. Every call runs inside the access of the person who signed in, so the AI sees the ConfigCat organizations, products and environments that person's API key already reaches and nothing more. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what ConfigCat itself allows.

Can my team share one ConfigCat connection?

Yes. One person connects ConfigCat in Elaichi and shares the connection with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every ConfigCat change.

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

Yes. Restrictions in Elaichi apply per action, so you can leave reading ConfigCat settings and change requests open while restricting deletes of products or proxy profiles, or restricting approvals entirely. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.

What happens to a ConfigCat connection when someone leaves?

Offboarding a person in Elaichi ends their access to ConfigCat at once, in every client they used. A shared ConfigCat connection keeps working for everyone else on the team. If you want ConfigCat gone altogether, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

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

Yes. ConfigCat 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 ConfigCat?

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

How is Elaichi different from Composio for ConfigCat?

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

Put ConfigCat 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