--- title: "Pendo MCP server for AI agents - actionlake" description: "Give Claude 61 Pendo actions through one MCP server: segments, guides, metadata. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/pendo updated: 2026-10-23 --- Connectors · Observability & analytics # Pendo MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Pendo and the rest of your systems. It gives your agent 61 Pendo actions (36 reads, 17 writes and 8 that wait for a confirmation) and holds the Pendo credential itself, so the agent never does. It paces Pendo's limits and records every call. [Connect Pendo free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "pendo.segments.list", intent: "check which Pendo account is connected" } # List shared segments · read · 1 upstream call ``` - 61 actions in one signed file - 36 read look, never change - 17 write create and update - 8 wait for a yes destructive, confirmed first Set up ## Connect Pendo in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Pendo. API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `integration_key` Pendo integration key - `host` Where your Pendo lives: your host ``` account { op: "connections.requirements", service: "pendo" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "pendo.segments.list" } # list shared segments · read · 1 upstream call check { action: "pendo.segments.create_visitor_segment", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Pendo at a glance **Sign-in** API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `integration_key` **Setup fields** `host` **Limits we pace to** 10 calls a second, per connection **API covered** Pendo Engage API v1 (Postman collection 16265887), at your Pendo instance's API base URL, which you enter when connecting **Built from** Pendo's documentation, read 23 October 2026[engageapi.pendo.io](https://engageapi.pendo.io/api/collections/16265887/Tzm6jvKG?segregateAuth=true&versionTag=latest) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 35 of 36 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 2, so ask can line Pendo up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Pendo. 61 actions in 16 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **36** read look, never change - **17** write create and update - **8** destructive wait for a confirmation 1. ### Segments 12 4 read · 6 write · 2 destructive List shared segments · Create a visitor segment from a list · Get a segment · Update a segment 2. ### Guides 10 4 read · 4 write · 2 destructive List Guides · Get Guides by ID · Get a Guide's change history · Get the guide order 3. ### Metadata 10 4 read · 5 write · 1 destructive Create or undelete metadata fields · Delete a metadata field · List dependencies of all metadata fields · Set metadata values for many visitors or accounts 4. ### Bulk deletions 4 2 read · 0 write · 2 destructive List outstanding bulk deletion requests · Get a bulk deletion request · Bulk delete accounts (GDPR/CCPA) · Bulk delete visitors (GDPR/CCPA) 5. ### Feedback 4 1 read · 2 write · 1 destructive Create feedback · Get feedback options · Update feedback · Delete feedback items 6. ### Servers 3 3 read · 0 write · 0 destructive List servers · List excluded or staging servers · Get a server by name 7. ### Visitors 3 3 read · 0 write · 0 destructive Get a Visitor · Get a Visitor by base64-encoded ID · Get a Visitor's activity history 8. ### Accounts 2 2 read · 0 write · 0 destructive Get an Account · Get an Account by base64-encoded ID **8 more areas · 13 actions** - Exclude list **2** - Features **2** - Pages **2** - Reports **2** - Track types **2** - Aggregation **1** - Surveys **1** - Token **1** Top actions ## The Pendo API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 14 of Pendo's 16 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `pendo.reports.list` List public reports | List public reports. | read | `analytics.report.list` 37 connectors | | `pendo.segments.list` List shared segments | List shared segments. | read | `analytics.segment.list` 17 connectors | | `pendo.aggregation.run` Run an aggregation query | Run an aggregation query. | read | `analytics.query_result.query` 2 connectors | | `pendo.visitors.get` Get a Visitor | Get a Visitor. | read | `analytics.profile.get` 4 connectors | | `pendo.track_types.list` List Track Types | List Track Types. | read | `analytics.tracked_event.list` 10 connectors | | `pendo.segments.create_visitor_segment` Create a visitor segment from a list | Create a visitor segment from a list. | write | `analytics.segment.create` 10 connectors | | `pendo.features.list` List Features | List Features. | read | this connector | | `pendo.segments.update` Update a segment | Update a segment. | write | `analytics.segment.update` 10 connectors | | `pendo.segments.delete` Delete a segment | Delete a segment. | destructive | `analytics.segment.delete` 10 connectors | | `pendo.track_types.get` Get a Track Type | Get a Track Type. | read | `analytics.tracked_event.get` 5 connectors | | `pendo.metadata.create_fields` Create or undelete metadata fields | Create or undelete metadata fields. | write | `platform.custom_field.create` 46 connectors | | `pendo.pages.list` List Pages | List Pages. | read | this connector | Try it ## Prompts to paste into Claude. Each one names the Pendo actions it will call, so you know what it reads and what it changes before you send it. 1. Read read List shared segments in Pendo and tell me what stands out. calls `pendo.segments.list` 2. Write write Create a visitor segment from a list in Pendo. Show me exactly what you will send before you save it. calls `pendo.segments.create_visitor_segment` Governance for Pendo ## Destructive actions wait for a yes. 8 Pendo actions are destructive. These are all of them: - Delete a segment `pendo.segments.delete` - Remove a visitor from a segment `pendo.segments.remove_visitor` - Delete a metadata field `pendo.metadata.delete_field` - Delete feedback items `pendo.feedback.delete` - Reset a staged Guide `pendo.guides.reset_staged` - Reset all staged Guides `pendo.guides.reset_all_staged` - Bulk delete accounts (GDPR/CCPA) `pendo.bulk_deletions.delete_accounts` - Bulk delete visitors (GDPR/CCPA) `pendo.bulk_deletions.delete_visitors` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do pendo.segments.delete confirm_policy: **human** Delete a segment? **intent:** the user asked me to delete a segment run suspended · waiting for a named person · key _pendo-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "pendo-agent", allowed_actions: ["pendo.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "pendo.segments.delete", approver: "lead@example.com" }, { match: "pendo.segments.remove_visitor", approver: "lead@example.com" }, { match: "pendo.metadata.delete_field", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Pendo only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Pendo costs on actionlake. Every Pendo action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Pendo refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 61 Pendo actions - 61 actions page each page of a long list is one call - 35 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Pendo action. 61 actions by area: the id your agent calls, what it does, and its effect. **Segments 12** - `pendo.segments.add_visitor` Add a visitor to a segment write - `pendo.segments.create_account_segment` Create an account segment from a list write - `pendo.segments.create_visitor_segment` Create a visitor segment from a list write - `pendo.segments.delete` Delete a segment destructive - `pendo.segments.get` Get a segment read - `pendo.segments.get_status` Get segment processing status read - `pendo.segments.get_visitor_export_status` Get a segment visitor export's status read - `pendo.segments.list` List shared segments read - `pendo.segments.patch_visitors` Add or remove a batch of visitors in a segment write - `pendo.segments.remove_visitor` Remove a visitor from a segment destructive - `pendo.segments.start_visitor_export` Start an export of a segment's visitors write - `pendo.segments.update` Update a segment write **Guides 10** - `pendo.guides.get` Get Guides by ID read - `pendo.guides.get_history` Get a Guide's change history read - `pendo.guides.get_order` Get the guide order read - `pendo.guides.list` List Guides read - `pendo.guides.reset_all_for_visitor` Reset all Guides' seen records for a visitor write - `pendo.guides.reset_all_staged` Reset all staged Guides destructive - `pendo.guides.reset_for_visitor` Reset a Guide's seen records for a visitor write - `pendo.guides.reset_staged` Reset a staged Guide destructive - `pendo.guides.set_segment` Change a Guide's segment write - `pendo.guides.set_state` Change a Guide's state write **Metadata 10** - `pendo.metadata.bulk_set_values` Set metadata values for many visitors or accounts write - `pendo.metadata.create_fields` Create or undelete metadata fields write - `pendo.metadata.delete_field` Delete a metadata field destructive - `pendo.metadata.get_field_dependencies` Get dependencies of a metadata field read - `pendo.metadata.get_schema` Get a metadata schema read - `pendo.metadata.get_value` Get a metadata field value read - `pendo.metadata.list_dependencies` List dependencies of all metadata fields read - `pendo.metadata.set_do_not_process` Set Do Not Process for a visitor or account write - `pendo.metadata.set_guide_opt_out` Opt a visitor or account out of guides write - `pendo.metadata.set_value` Set a metadata field value write **Bulk deletions 4** - `pendo.bulk_deletions.delete_accounts` Bulk delete accounts (GDPR/CCPA) destructive - `pendo.bulk_deletions.delete_visitors` Bulk delete visitors (GDPR/CCPA) destructive - `pendo.bulk_deletions.get` Get a bulk deletion request read - `pendo.bulk_deletions.list` List outstanding bulk deletion requests read **Feedback 4** - `pendo.feedback.create` Create feedback write - `pendo.feedback.delete` Delete feedback items destructive - `pendo.feedback.get_options` Get feedback options read - `pendo.feedback.update` Update feedback write **Servers 3** - `pendo.servers.get` Get a server by name read - `pendo.servers.list` List servers read - `pendo.servers.list_by_flag` List excluded or staging servers read **Visitors 3** - `pendo.visitors.get` Get a Visitor read - `pendo.visitors.get_by_base64_id` Get a Visitor by base64-encoded ID read - `pendo.visitors.get_history` Get a Visitor's activity history read **Accounts 2** - `pendo.accounts.get` Get an Account read - `pendo.accounts.get_by_base64_id` Get an Account by base64-encoded ID read **Exclude list 2** - `pendo.exclude_list.list` List excluded items read - `pendo.exclude_list.list_by_type` List excluded items of one type read **Features 2** - `pendo.features.get` Get Features by ID read - `pendo.features.list` List Features read **Pages 2** - `pendo.pages.get` Get Pages by ID read - `pendo.pages.list` List Pages read **Reports 2** - `pendo.reports.get_results` Get a report's results read - `pendo.reports.list` List public reports read **Track types 2** - `pendo.track_types.get` Get a Track Type read - `pendo.track_types.list` List Track Types read **Aggregation 1** - `pendo.aggregation.run` Run an aggregation query read **Surveys 1** - `pendo.surveys.list_responses` List Sentiment survey responses read **Token 1** - `pendo.token.verify` Verify the integration key read Questions ## The Pendo MCP server, answered. **Is there a Pendo MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 61 Pendo actions across segments, guides, metadata and bulk deletions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Pendo. **What do I need to connect Pendo?** Pendo integration key. Plus your host. The free call account { op: "connections.requirements", service: "pendo" } lists exactly what to paste. **Can an AI agent delete or change things in Pendo?** Only if its key allows it, and only with an explicit confirmation. 8 Pendo actions are destructive, including delete a segment, remove a visitor from a segment and delete a metadata field. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Pendo API limit?** actionlake paces every call to the limits in the Pendo service file: 10 calls a second per connection. Repeated reads are answered from cache (35 Pendo actions can be), which never reaches Pendo. **What does a Pendo action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (61 Pendo actions page). Cache hits, searches, dry runs and calls Pendo refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Pendo API does it cover?** The Pendo Engage API v1 (Postman collection 16265887) at your Pendo instance's API base URL, which you enter when connecting. It is built from Pendo's documentation as read on 23 October 2026. 61 actions in 16 areas, each one in the signed service file (version 1.0.0). **Does actionlake keep my Pendo data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Pendo credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Pendo Shares the most action names with - [PostHog 10](https://actionlake.com/connectors/posthog) - [Matomo 6](https://actionlake.com/connectors/matomo) - [Metabase 5](https://actionlake.com/connectors/metabase) - [Mixpanel 3](https://actionlake.com/connectors/mixpanel) - [RudderStack 2](https://actionlake.com/connectors/rudderstack) - [Amplitude 1](https://actionlake.com/connectors/amplitude) Joins with, on shared entities - [Docebo 1](https://actionlake.com/connectors/docebo) - [Infobip 1](https://actionlake.com/connectors/infobip) - [Splunk Platform 1](https://actionlake.com/connectors/splunk-platform) - [Cvent 1](https://actionlake.com/connectors/cvent) - [Klaviyo 1](https://actionlake.com/connectors/klaviyo) - [Dotdigital 1](https://actionlake.com/connectors/dotdigital) Browse - [All Observability & analytics connectors](https://actionlake.com/connectors/category/observability-and-analytics) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Pendo; the name is the vendor's own. Counts are from the Pendo service file, version 1.0.0. ## Give your agent Pendo today. [Connect Pendo free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/pendo More: https://actionlake.com/llms.txt