Connect your AI Agents to Pendo in minutes

Merge lets you securely connect your agents to Pendo and thousands of tools instantly

Available tools

get_account_metadata_schema

View available metadata fields for Pendo accounts, including field names and types. Use this to discover what metadata fields can be queried or written.

query_accounts

Retrieve Pendo account records matching metadata criteria. Max 50,000 results. Use offset for pagination.

get_account

Get a single Pendo account by ID. Returns all metadata fields. Use query_accounts to search for account IDs.

bulk_delete_accounts

Delete up to 500 Pendo accounts and all their associated data. Use for GDPR right-to-erasure requests. Use query_accounts to find account IDs.

upsert_account_metadata

Set custom metadata fields on a Pendo account. Pass metadata as a dict of field names to values. Use query_accounts to find valid account IDs.

query_activity

Query Pendo usage metrics by source: pageEvents, featureEvents, guideEvents, trackEvents, or pollEvents. Defaults to last 90 days. Pass start_time/end_time (epoch ms) to override. Max 367-day range. Max 1,000 records per call.

get_product_area_activity

Get page view activity for all pages in a Pendo product area. Max 367-day range. Defaults to last 90 days. Use offset for pagination. Max 10,000 records per call.

search_entities

Find Pendo items (Pages, Features, Track Events, guides) by name substring. Returns items whose names contain the query string (case-insensitive). Filter by entity_types to narrow results. Results are capped at 1,000 items per entity type.

list_segments

List all publicly shared Pendo segments with names and IDs. Segments define visitor/account cohorts for use in other queries.

list_pages

List all tagged pages in Pendo with their IDs, names, and URL rules. Use get_page to retrieve full details for a specific page. Use offset for pagination.

get_page

Get a single Pendo page definition by ID, including URL rules and app association. Use list_pages or search_entities to find page IDs.

list_features

List all tagged features (click targets) in Pendo with their IDs, names, and selectors. Use get_feature to retrieve full details for a specific feature. Use offset for pagination.

get_feature

Get a single Pendo feature definition by ID, including CSS selector and page association. Use list_features or search_entities to find feature IDs.

list_track_types

List all custom track event types instrumented in Pendo. Returns event names and IDs needed before querying trackEvents in query_activity. Use offset for pagination.

list_guides

List Pendo guides, optionally filtered by state or type. Returns ID, name, description, state, and scheduling info. Use offset for pagination. Max 1,000 guides per call.

get_guide

Get a single Pendo guide by ID. Returns full definition including steps, targeting, and scheduling. Use list_guides to find valid guide IDs.

get_guide_metrics

Get performance data for a Pendo guide: views, completions, dismissals. Max 93-day range. Defaults to last 90 days. Counts are based on up to 10,000 raw events — results may be underreported for high-volume guides. Use list_guides to find guide IDs.

validate_credential

Validate Pendo credentials by querying the visitors pipeline. Returns success and message.

get_visitor_metadata_schema

View available metadata fields for Pendo visitors, including field names and types. Use this to discover what metadata fields can be queried or written.

query_visitors

Retrieve Pendo visitor records matching metadata criteria. Max 50,000 results. Always excludes anonymous visitors. Use offset for pagination.

get_visitor

Get a single Pendo visitor by ID. Returns all metadata fields. Use query_visitors to search for visitor IDs.

bulk_delete_visitors

Delete up to 500 Pendo visitors and all their associated events. Use for GDPR right-to-erasure requests. Use query_visitors to find visitor IDs.

upsert_visitor_metadata

Set custom metadata fields on a Pendo visitor. Pass metadata as a dict of field names to values. Use query_visitors to find valid visitor IDs.

View all tools by creating a free accountSee more tools

How to set up Merge Agent Handler

In an mcp.json file, add the configuration below, and restart Cursor.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Copy Code

Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.

Make sure Claude is using the Node v20+.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote@latest",
8        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9        "--header",
10        "Authorization: Bearer ${AUTH_TOKEN}"
11      ],
12      "env": {
13        "AUTH_TOKEN": "yMt*****"
14      }
15    }
16  }
17}
Copy Code
Copied!

Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.

Learn more in the official documentation ↗

1{
2    "mcpServers": {
3      "agent-handler": {
4        "command": "npx",
5        "args": [
6          "-y",
7          "mcp-remote@latest",
8          "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9          "--header",
10          "Authorization: Bearer ${AUTH_TOKEN}"
11        ],
12        "env": {
13          "AUTH_TOKEN": "<ah-production-access-key>"
14        }
15      }
16    }
17  }
Copy Code

In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".

You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.

Learn more in the official documentation ↗

1{
2  "inputs": [
3    {
4      "type": "promptString",
5      "id": "agent-handler-auth",
6      "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7      "password": true
8    }
9  ],
10  "servers": {
11    "agent-handler": {
12      "type": "stdio",
13      "command": "npx",
14      "args": [
15        "-y",
16        "mcp-remote@latest",
17        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18        "--header",
19        "Authorization: Bearer ${input:agent-handler-auth}"
20      ]
21    }
22  }
23}
Copy Code

FAQs on using Merge's Pendo  MCP server

FAQs on using Merge's Pendo  MCP server

Explore other MCP servers built and managed by Merge

freshbooks
FreshBooks
freshdesk
Freshdesk
freshservice
Freshservice
front
Front
gamma
Gamma
github
GitHub
gitlab
GitLab
gmail
Gmail
gong
Gong
google_bigquery
Google BigQuery
google_calendar
Google Calendar
google_docs
Google Docs
google_drive
Google Drive
google_maps
Google Maps
google_meet
Google Meet
google_sheets
Google Sheets
google_slides
Google Slides
google_tasks
Google Tasks
grafana
Grafana
greenhouse
Greenhouse
guru
Guru
hex
Hex
hibob
HiBob
hubspot
HubSpot

Ready to try it out?

Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now