Pendo MCP server

What the model can do

Pendo product analytics: tagged pages and features, in-app guides and their status, one visitor's or account's first and last visit and metadata, shared segments and reports, and survey and NPS responses. With a write-access key, can publish or switch off a guide, retarget it, reset it for one visitor, log and edit Listen feedback, manage API-made segments, and erase named visitors, when asked.

Reads

• pendo_list_pagesPages tagged in Pendo (the screens of the product it tracks): name, app, who made it and when it was last changed.
• pendo_list_featuresFeatures tagged in Pendo (buttons and elements whose clicks it counts): name, app, product area, who made it and when it was last changed.
• pendo_list_guidesIn-app guides in Pendo (walkthroughs, announcements, polls): name, status (public, draft, disabled…), description and a short excerpt of the content.
• pendo_get_visitorOne Pendo visitor by their visitor id (often their email or your app's user id): accounts they belong to, first and last visit…
• pendo_get_accountOne Pendo account (a customer company) by its account id: first and last visit, and the metadata your app sends Pendo about it (such as plan or ARR).
• pendo_list_segmentsShared Pendo segments (saved groups of visitors or accounts): name, id and who made it.
• pendo_list_reportsPublic reports saved in Pendo: name, id, kind and who made it.
• pendo_survey_responsesResponses to one Pendo survey (NPS, poll or survey guide), newest first: the survey's overall score and sentiment counts…

Acts, when you ask

These change something in Pendo. 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.

• pendo_set_guide_stateChanges an in-app Pendo guide's state.
• pendo_set_guide_segmentChanges which shared segment an in-app Pendo guide targets (segment id from pendo_list_segments), or everyone=true to show it to every user.
• pendo_reset_guide_for_visitorErases one visitor's record of having seen one Pendo guide, so the guide shows to them again in the product.
• pendo_create_feedbackLogs a new feedback request in Pendo Listen on behalf of a customer account (and optionally one of its visitors), for one or more apps…
• pendo_update_feedbackEdits a Pendo Listen feedback request by its id: title, description, importance, labels or product areas.
• pendo_delete_feedbackPermanently deletes Pendo Listen feedback requests by id (at most ten, each named).
• pendo_create_segmentCreates a new shared Pendo segment from an explicit list of visitor ids or account ids (at most 1,000 here).
• pendo_update_segmentRenames a Pendo segment that was created through the API, and/or REPLACES its whole visitor list with the ids given (at most 1,000 here…
• pendo_patch_segment_visitorsAdds and/or removes named visitors in a Pendo segment that was created through the API (at most 1,000 visitors in one call, Pendo's limit).
• pendo_delete_segmentPermanently deletes one Pendo segment.
• pendo_delete_visitorsPermanently erases named visitors and all their data from Pendo (its GDPR/CCPA deletion), at most 50 ids, each given explicitly.

Connect it

First connect Pendo on Dashboard → Connections, then add Memtro to your client once. The Pendo 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 Pendo 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

• › When did the Northwind account last visit the product?
• › Which in-app guides are still in draft?
• › What did detractors say in last month's NPS survey?
• › When was priya.nair@acme.example first and last seen in Pendo?
• › Switch off the old billing guide and publish the new one to the Enterprise segment

Questions

Is this an official Pendo MCP server?

No. It is Memtro's MCP server with Memtro's Pendo connector behind it: the connector reads Pendo through its API with the credentials you connect on Dashboard → Connections, and Pendo 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 Pendo?

Only when you ask, and only what it has been granted: publish, stage, disable or return to draft an in-app guide (changes what users see in the product); change which segment an in-app guide targets; let one visitor see a guide again (erases their seen record for it); log a feedback request in Pendo Listen for an account; edit a Listen feedback request; delete up to ten Listen feedback requests (permanent); create a shared segment from a list of visitor or account ids; rename an API-made segment or replace its visitor list; add or remove visitors in an API-made segment; delete a segment (permanent); erase named visitors and their data from Pendo (GDPR/CCPA, permanent). 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