Chameleon MCP server

What the model can do

Chameleon in-product tours and microsurveys: tours and microsurveys with live state and started, completed and exited counts, microsurvey answers (what was said, not who said it), tour interactions by state, segments, tags, environments and pending deliveries; when you ask, can publish or unpublish tours, publish microsurveys, tag them, change their environments, show a tour or microsurvey to one named end user, reschedule or cancel that delivery, update a user profile's properties, track an event, clear or permanently delete a user profile, delete a response and delete a company.

Reads

• chameleon_toursChameleon tours (banners, modals, walkthroughs), newest first: name, live or not, scheduled publish or unpublish, all-time started…
• chameleon_surveysChameleon microsurveys, newest first: name, live or not, schedule, all-time started, completed and exited counts, dropdown options chosen so far…
• chameleon_survey_responsesAnswers to one Chameleon microsurvey, newest first: the button chosen, dropdown choices, comments, when finished and on which page…
• chameleon_tour_interactionsHow end users went through one Chameleon tour, newest first: each interaction's state (started, completed, exited, displayed), when…
• chameleon_segmentsChameleon segments (audiences) with their filter rules: property, operator and value, joined by and/or.
• chameleon_tagsChameleon tags (Upsell, Onboarding…) with how many tours and microsurveys carry each; the ids are what chameleon_tag_experience takes.
• chameleon_environmentsChameleon environments (groups of domains such as Production or Staging); the ids are what chameleon_set_experience_environment takes.
• chameleon_deliveriesDeliveries (a tour or microsurvey queued for one end user), newest first: which experience, for which profile id, the time window…

Acts, when you ask

These change something in Chameleon. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• chameleon_publish_tourPublishes a Chameleon tour so it goes live to every end user it targets on their next page load, or unpublishes it…
• chameleon_publish_surveyPublishes a Chameleon microsurvey now, so it goes live to every end user it targets on their next page load.
• chameleon_tag_experienceAdds a tag to a Chameleon tour or microsurvey, or removes it (remove true).
• chameleon_set_experience_environmentAdds an environment (a group of domains such as Production) to a Chameleon tour or microsurvey, or removes it (remove true)…
• chameleon_deliver_experienceQueues a live Chameleon tour or microsurvey for one named end user of your product (by profile_id, your uid, or email)…
• chameleon_update_deliveryChanges a pending Chameleon delivery's time window or conditions (from, until, once, use_segmentation).
• chameleon_cancel_deliveryCancels a pending Chameleon delivery so the tour or microsurvey is not shown to that person; one that already triggered cannot be cancelled.
• chameleon_update_profileCreates or updates one end user's profile in Chameleon by your uid, setting the properties given…
• chameleon_track_eventRecords an event (such as "Imported data") against one end user by your uid; events feed segments and goals…
• chameleon_clear_profileClears one end user's Chameleon profile: resets its browser and activity data, removes their microsurvey responses and tracked events…
• chameleon_forget_profilePermanently deletes one end user from Chameleon with everything recorded about them (experiences, events, metrics), as for a data-deletion request…
• chameleon_delete_responsePermanently deletes one Chameleon microsurvey response, and its contribution to the survey's metrics and summaries.
• chameleon_delete_companyPermanently deletes one company record from Chameleon and detaches it from every user profile linked to it (the profiles themselves stay).

Connect it

First connect Chameleon on Dashboard → Connections, then add Memtro to your client once. The Chameleon tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Chameleon connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › How many people completed the onboarding tour?
• › What did people say in the pricing microsurvey this week?
• › Which tours are live right now?
• › Which deliveries are still pending?
• › Unpublish the old billing banner.

Questions

Is this an official Chameleon MCP server?

No. It is Memtro's MCP server with Memtro's Chameleon connector behind it: the connector reads Chameleon through its API with the credentials you connect on Dashboard → Connections, and Chameleon publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Chameleon?

Only when you ask, and only what it has been granted: publish or unpublish a tour; publish a microsurvey; add or remove a tag on a tour or microsurvey; add or remove an environment on a tour or microsurvey; show a tour or microsurvey to one named end user (create a delivery); reschedule a pending delivery; cancel a pending delivery; create or update an end user's profile properties; track an event for an end user; clear an end user's profile data; permanently delete an end user's profile; delete a microsurvey response; delete a company. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Analytics

• Google Analytics 4 MCP server
• Plausible Analytics MCP server
• Umami MCP server
• Google Search Console MCP server
• Segment MCP server
• App Store Connect MCP server