Product Development
Chameleon MCP connector
The Chameleon connector lets Claude, ChatGPT, Cursor and the Elaichi Agent look up Chameleon user profiles, companies, segments, tours and tour interactions, update a tour, and remove a profile, all inside each person's own Chameleon access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Chameleon to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Chameleon once
-
Open Connections, choose Add connection, and pick Chameleon.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Chameleon API key. One person generates a token in Chameleon and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Chameleon 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.
Chameleon 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 today. The plugin directory lives at chatgpt.com/plugins.
Chameleon 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.
Connect Chameleon 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.
Use cases
What teams do with Chameleon through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Product
See how a product tour is performing
Ask which steps of your onboarding tour people finish and where they stop, pulled straight from Chameleon tour interactions without opening the Chameleon dashboard.
-
Customer Success
Check what a customer has seen before a call
Before a renewal call, look up the company in Chameleon and see which profiles belong to it and which tours they have completed, so you know what they have and have not been shown.
-
Support
Find out if a user saw the walkthrough
When someone writes in confused about a feature, look up their Chameleon profile and check whether the feature tour reached them and how far they got.
-
Growth
Count who falls into a segment
Ask how many profiles or companies match a Chameleon segment and which experiences already target it before you plan a new launch or in-app announcement.
-
Product Operations
Tidy up a tour without leaving chat
Rename a Chameleon tour or change its settings in plain language, then confirm the change landed by asking for the tour again.
-
Privacy
Handle a deletion request properly
When a user asks to be removed, delete or forget their Chameleon profile from the chat, with the action written to the audit log under the name of the person who did it.
Try asking
- “Which steps of the onboarding tour do people drop off at?”
- “How many profiles at Acme have finished the billing tour?”
- “Which experiences target the enterprise trial segment?”
Compare
Elaichi vs Zapier MCP vs Composio for Chameleon
All three can connect Chameleon 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 Chameleon tools | Allow or restrict single Chameleon 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 Chameleon 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 | $15 per user per month. | 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.
AI tools
Chameleon tools for your AI agents
97 tools are ready to call through Elaichi's MCP endpoint the moment you connect Chameleon, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Chameleon gets you
6 screens from the product, each doing one job for your Chameleon account.
The agent
Ask Chameleon questions in plain language.
Which tours did this company finish, answered from live Chameleon profiles and interactions.
- profiles
- companies
- segments
- tours
Ask Elaichi to work across your apps.
Which steps of the onboarding tour do people drop off at?
How many profiles at Acme have finished the billing tour?
Which experiences target the enterprise trial segment?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Chameleon works in every MCP client you use.
Claude, ChatGPT and Cursor reach Chameleon through one org endpoint, no SDK, no shared key.
Copy the endpoint
Tool catalog
97 Chameleon tools, ready without writing code.
Profiles, companies, segments, tours and tour interactions, each with its own resources and methods.
- Chameleon account verify
- List all Chameleon profiles
- Chameleon profiles search
- Chameleon profiles count
Toolboxes
Every team gets its own Chameleon toolbox.
Product sees tours, Success sees profiles and companies, Privacy handles removals, each scoped separately.
- Product
- Customer Success
- Support
- Growth
Shared connections
Share one Chameleon connection, keep the key private.
One person connects Chameleon, teams and members work through it without seeing the API key.
- Product
- Customer Success
- Support
- Growth
Audit log
Every Chameleon call is logged, nothing is lost.
See who looked up a profile, updated a tour or deleted a record, and when.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns Chameleon interactions into work.
Tour interactions are fetched, grouped and drafted into a digest, approved, then posted back to Chameleon.
Chameleon digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch profiles
Chameleon
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 Michael Brennan
Approve Deny -
Post the digest
Chameleon
Queued
Collections and dashboards
Chameleon numbers, computed on a schedule, no model.
Four metrics, fourteen days of new profiles and a team breakdown, refreshed without anyone asking.
Chameleon health
Refreshed 4 minutes ago · every 15 minutes · from the profiles collection
Profiles
1,284 ↓ 12%
Companies
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Profiles created
Last 14 days
By team
Share of activity
Product 34%
Customer Success 27%
Support 21%
Growth 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Chameleon to Claude?
It takes two steps. In Elaichi, choose Chameleon and paste in an API key from your Chameleon account; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Chameleon is available in Claude.
Does Chameleon work with ChatGPT and Cursor as well as Claude?
Yes. Once Chameleon is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Chameleon once and every client you use picks it up.
What can an AI agent actually do with my Chameleon data?
It can look up and search Chameleon user profiles and companies, count how many match a segment, list the experiences aimed at a segment, pull up tours and the interactions people have had with them, update a tour, and delete or forget a profile when asked. In practice that means questions like which tours a customer finished or where people drop out of onboarding. Short, concrete asks work better than long paragraphs.
Does connecting Chameleon give the AI my whole account?
No. Every call to Chameleon runs as the person who signed in, so the agent sees the profiles, companies, segments and tours that person could already see in Chameleon. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Chameleon itself allows.
Can I stop an agent from deleting or changing things in Chameleon?
Yes. Restrictions in Elaichi work per action, so you can allow reading Chameleon profiles and tours while blocking profile deletion, forgetting a profile, or updating a tour. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.
What happens to a Chameleon connection when someone leaves?
Offboarding them in Elaichi ends their access to Chameleon through every client at once. A Chameleon connection shared with the team keeps working for everyone else. If you want it gone entirely, disconnecting Chameleon once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Chameleon MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Chameleon 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, 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 Chameleon?
Yes. Both let Claude, ChatGPT or Cursor use Chameleon. 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 Chameleon call.
How is Elaichi different from Composio for Chameleon?
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 Chameleon: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Chameleon in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.