Skip to content

Pendo (Japan) MCP connector

The Pendo (Japan) connector links your Japan Pendo subscription to Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can ask about visitors, accounts, segments and product usage while every call runs inside each person's own access.

  • How it connects. Connects over OAuth. 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 Pendo (Japan) to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Pendo (Japan) once

  1. Open Connections, choose Add connection, and pick Pendo (Japan).

  2. Optionally set Share with to give a team access, then press Connect.

  3. Approve it in Pendo (Japan). Pendo (Japan)'s own window opens. Whoever approves it decides what this connection can reach.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

pendo (japan)
Pendo (Japan)
Allium
Amplitude
Artie
AthenaHQ
Botify
2

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.

Pendo (Japan) MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Pendo (Japan) MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Pendo (Japan) MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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 Pendo (Japan) to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Pendo (Japan) through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Product

    Check how a product area is landing

    Ask how usage of a product area has moved week over week and which accounts drive it. Get the engagement score back without opening a dashboard.

  • Customer Success

    Prepare an account review from live usage

    Before a quarterly review, pull an account's app usage, the visitors who are active, and where usage has dropped off since last quarter.

  • Support

    See what a visitor did before the ticket

    When a ticket arrives, ask what the visitor touched in the last few days and which product areas they spent time in, then answer with context.

  • Product Marketing

    Build a segment for the next launch

    Describe the users you want, for example accounts that have not tried a new area yet, and have the segment created in Pendo in Japan ready to target.

  • Sales

    Spot adoption gaps before a renewal

    Ask which features an account has never used and how its usage compares with similar accounts, so the renewal conversation starts with facts.

  • Leadership

    Get a usage trend across every application

    Ask for application usage over the last 90 days across all your Pendo applications in Japan, grouped by month, in one plain question.

Try asking

  • “Which accounts dropped in app usage over the last 30 days?”
  • “Show visitor activity for the Acme account this week.”
  • “Build a segment of visitors who used reporting twice this month.”

See all 87 Pendo (Japan) tools below

Compare

Elaichi vs Zapier MCP vs Composio for Pendo (Japan)

All three can connect Pendo (Japan) to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Pendo (Japan), by what to check
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 Pendo (Japan) tools Allow or restrict single Pendo (Japan) 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 Pendo (Japan) 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

Pendo (Japan) tools for your AI agents

87 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pendo (Japan), governed by the same roles, restrictions, and audit log as everything else in Elaichi. Pendo (Japan) builds and runs these tools.

See it in Elaichi

What connecting Pendo (Japan) gets you

6 screens from the product, each doing one job for your Pendo (Japan) account.

The agent

Ask about visitors and accounts in plain language.

Three starter prompts, answers drawn from live Pendo (Japan) usage records.

  • visitors
  • accounts
  • segments
  • product areas

Ask Elaichi to work across your apps.

Which accounts dropped in app usage over the last 30 days?

Show visitor activity for the Acme account this week.

Build a segment of visitors who used reporting twice this month.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One governed endpoint reaches Pendo (Japan) everywhere.

Claude, ChatGPT and Cursor share one org endpoint, with no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

87 Pendo (Japan) tools, ready without code.

Segments, visitors, accounts, product areas and usage, every tool cataloged with its resource and method.

  • List all applications
  • Search entities
  • Segment list
  • Get entity
ElaichiTools
Tool Action Description
List all applications List Retrieve a list of subscriptions and applications you have access to. Often used as a first step with other tools (for example, passing App IDs to aggregateEntityUsage for usage data). Also confirms which application data you have access to through authentication.
Search entities Search Find Pendo items by name or conceptual meaning, including Pages, Features, Track Events, accounts, and saved clips. (Deprecated for guides and product areas).
Segment list List List all publicly shared segments with their names and IDs.
Get entity Get Retrieve the full configuration of a single Page, Feature, Track Event, or guide by its exact ID. Returns URL rules for Pages, element rules and Page context for Features, event rules for Track Events, and ordered steps, polls, and interactive elements for guides. Doesn't…
List custom objects List List the custom event properties designated as business objects. Returns each object's underlying field and kind, customer-facing display name and description when configured, and the date it was promoted to an object.

Toolboxes

Every team gets its own Pendo (Japan) toolbox.

Product sees engagement scores, Customer Success sees account usage, each scoped to the team.

  • Product
  • Customer Success
  • Support
  • Product Marketing
ElaichiToolboxes
Name Source template Tools Created

Product toolbox

Pendo (Japan) · feature usage and engagement scores

Pendo (Japan) starter 18 Mar 4, 2026

Customer Success toolbox

Pendo (Japan) · account usage and health

— 9 Mar 2, 2026

Support toolbox

Pendo (Japan) · visitor activity

— 24 Feb 27, 2026

Product Marketing toolbox

Pendo (Japan) · segments and launches

Pendo (Japan) starter 6 Feb 19, 2026

Sales toolbox

Pendo (Japan) · account adoption before renewals

— 31 Jan 30, 2026

Leadership toolbox

Pendo (Japan) · application usage trends

— 12 Jan 22, 2026

Shared connections

Share a Pendo (Japan) connection, never a credential.

One person connects, teams and members work through it, and nobody else sees a secret.

  • Product
  • Customer Success
  • Support
  • Sales Japan
ElaichiConnections
Connection Scope Status Access
PE

Pendo (Japan) (Product)

Connected by Emily Carter

Personal • Active 1 team · 6 members
PE

Pendo (Japan) (Customer Success)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
PE

Pendo (Japan) (Support)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
PE

Pendo (Japan) (Sales Japan)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
PE

Pendo (Japan) (Marketing)

Connected by Ryan Hayes

Personal • Active Not shared
PE

Pendo (Japan) (Leadership)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Pendo (Japan) call is written down.

When, who, what happened, type and resource, in an append-only log you can answer from.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Pendo (Japan) Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Pendo (Japan) Visitors Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Pendo (Japan) Visitors List Toolbox

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

The schedule fires and the work begins.

Pendo (Japan) usage is fetched, grouped and drafted into a digest, approved, then posted back.

Pendo (Japan) digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch visitors

    Pendo (Japan)

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Pendo (Japan)

    Queued

Collections and dashboards

Pendo (Japan) health, computed without a model.

Four metrics, 14 days of segments created and a team breakdown, refreshed on a schedule.

Pendo (Japan) health

Refreshed 4 minutes ago · every 15 minutes · from the visitors collection

Live

Visitors

1,284 ↓ 12%

Accounts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Visitors created

Last 14 days

By team

Share of activity

Product 34%

Customer Success 27%

Support 21%

Sales Japan 18%

FAQ

Frequently asked questions

How do I connect Pendo in Japan to Claude?

In Elaichi, choose the Pendo (Japan) connector and connect it; Pendo in Japan opens its own sign-in page, you approve access, and you are done. 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 https://api.elaichi.ai/mcp. Pendo in Japan appears in Claude the next time you start a conversation.

Does Pendo in Japan work with ChatGPT and Cursor as well as Claude?

Yes. Once Pendo (Japan) 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 Pendo in Japan once and every client uses that one connection.

What can an AI agent actually do with my Pendo data in Japan?

With Pendo in Japan connected, an agent can look up visitors and accounts, read their activity, report usage of an application or a product area over time, and give you the product engagement score. It can also list, build, update or remove segments, and show you the metadata you track on accounts and visitors. Short, concrete asks such as "app usage for Acme, last 30 days" work better than long paragraphs.

Does connecting Pendo in Japan give the AI access to every application and segment?

No. Access to Pendo in Japan follows the person who signed in, so the agent sees only the applications, visitors, accounts and segments that person can already see in Pendo. Elaichi can narrow that access further with roles and restrictions, but it never widens it beyond what Pendo in Japan already allows.

Can my team share one Pendo connection in Japan?

Yes. One person connects Pendo (Japan) in Elaichi and shares the connection with a team, and nobody else ever handles a credential or sign-in secret. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every call to Pendo in Japan.

Can I stop an agent from deleting or changing segments in Pendo in Japan?

Yes. Restrictions in Elaichi work per action, so you can allow reading usage and visitor activity from Pendo in Japan while blocking anything that creates, updates or deletes segments. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however it is worded, can reach it.

What happens to a Pendo connection in Japan when someone leaves?

Offboarding a person in Elaichi ends their access to Pendo in Japan at once, across every client they used. A connection they shared keeps working for everyone else on the team. If you ever want Pendo (Japan) gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

Does the Pendo (Japan) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Pendo (Japan) 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 Pendo (Japan)?

Yes. Both let Claude, ChatGPT or Cursor use Pendo (Japan). 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 Pendo (Japan) call.

How is Elaichi different from Composio for Pendo (Japan)?

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 Pendo (Japan): one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Pendo (Japan) in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor 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.