Skip to content

CRM

Planhat MCP connector

The Planhat connector brings companies, end users, invoices, campaigns and issues into Claude, ChatGPT, Cursor and any MCP client through one governed endpoint, where each person works inside their own Planhat access and every action is logged.

  • How it connects. Connects with an API key. 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 Planhat to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Planhat once

  1. Open Connections, choose Add connection, and pick Planhat.

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

  3. Paste a Planhat API key. One person generates a token in Planhat and pastes it once. Everyone else works through Share with, and never sees it.

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

Add connection

Choose a connector.

planhat
Planhat
Affinity
Attio
Clazar
Clio Manage
Close
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.

Planhat 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.

Planhat 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.

Planhat 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 Planhat 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 Planhat through Elaichi

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

  • Customer Success

    Catch a company record up after a call

    After a check-in, tell the agent what changed and it updates the Planhat company for you, so the account picture stays current without opening another tab.

  • Customer Success

    Log an issue while the customer is talking

    Create a Planhat issue against the right company the moment a customer raises a problem, then update it as the fix moves along.

  • Support

    See every end user at an account

    Before replying to a ticket, ask who the end users are at that company in Planhat and which issues are already open for them.

  • Finance

    Check invoices before a renewal conversation

    Pull up the invoices on a Planhat company and spot anything overdue or missing before the account team walks into the renewal call.

  • Marketing

    Set up and tidy customer campaigns

    Create a Planhat campaign, update its details as the plan changes, and list what is running so you know what customers are already receiving.

  • Revenue Operations

    Add new customers without retyping

    When a deal closes, create the Planhat company and its end users from the handover notes in one ask, instead of copying fields by hand.

Try asking

  • “Which Planhat companies have open invoices over 30 days?”
  • “Summarize campaign performance across our Planhat accounts this quarter.”
  • “Create a Planhat company for the account we signed yesterday.”

See all 143 Planhat tools below

Compare

Elaichi vs Zapier MCP vs Composio for Planhat

All three can connect Planhat 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 Planhat, 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 Planhat tools Allow or restrict single Planhat 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 Planhat 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

Planhat tools for your AI agents

143 tools are ready to call through Elaichi's MCP endpoint the moment you connect Planhat, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Planhat gets you

6 screens from the product, each doing one job for your Planhat account.

The agent

Ask in plain language, answer from Planhat.

Starter prompts pull live companies, campaigns and invoices straight from Planhat.

  • companies
  • campaigns
  • invoices
  • end users

Ask Elaichi to work across your apps.

Which Planhat companies have open invoices over 30 days?

Summarize campaign performance across our Planhat accounts this quarter.

Create a Planhat company for the account we signed yesterday.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Planhat.

One org MCP endpoint over OAuth, 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

143 Planhat tools, ready without custom code.

Browse every Planhat resource and method, from companies to invoices to campaigns.

  • List all Planhat campaigns
  • Get single Planhat campaign by ID
  • Update a Planhat campaign by ID
  • Create a Planhat campaign
ElaichiTools
Tool Action Description
List all Planhat campaigns List List Planhat campaigns you are running inside companies, e.g. to drive adoption or deepen stakeholder relations. Returns campaigns with _id, name, campaignPurpose, companyId, and companyName.
Get single Planhat campaign by ID Get Get a single Planhat campaign by id. Returns: _id, name, campaignPurpose, companyId, companyName, externalId, sourceId, custom, __v, usage. Required: id (Planhat _id; externalId/sourceId prefixed identifiers are also accepted).
Update a Planhat campaign by ID Update Update a Planhat campaign by id. Returns the updated campaign with _id, name, campaignPurpose, companyId, and companyName. Required: id (Planhat _id; externalId/sourceId prefixed identifiers are also accepted).
Create a Planhat campaign Create Create a Planhat campaign. Returns the created campaign with _id, name, campaignPurpose, companyId, and companyName. Requires name and companyId (a company externalId or sourceId may be passed instead, prefixed with extid- or srcid-).
Delete a Planhat campaign by ID Delete Delete a Planhat campaign by id. Returns: n, ok, deletedCount. Required: id.

Toolboxes

Every team gets its own Planhat toolbox.

Curate a scoped set of Planhat tools per team from one list.

  • Customer Success
  • Sales
  • Marketing
  • Finance
ElaichiToolboxes
Name Source template Tools Created

Customer Success toolbox

Planhat · companies and health

Planhat starter 18 Mar 4, 2026

Sales toolbox

Planhat · accounts and end users

— 9 Mar 2, 2026

Marketing toolbox

Planhat · campaigns and segments

— 24 Feb 27, 2026

Finance toolbox

Planhat · invoices and licenses

Planhat starter 6 Feb 19, 2026

Support toolbox

Planhat · conversations and issues

— 31 Jan 30, 2026

Operations toolbox

Planhat · workflows and assets

— 12 Jan 22, 2026

Shared connections

Share a Planhat account, never the credential.

See who connected each account and how many teams and members use it.

  • Success EMEA
  • Sales AMER
  • Marketing
  • Finance
ElaichiConnections
Connection Scope Status Access
PL

Planhat (Success EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
PL

Planhat (Sales AMER)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
PL

Planhat (Marketing)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
PL

Planhat (Finance)

Connected by Tyler Reed

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

Planhat (Support)

Connected by Ryan Hayes

Personal • Active Not shared
PL

Planhat (Enterprise Accounts)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Planhat call is on the record.

When, who, what happened, type and resource, appended for each Planhat action.

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

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Planhat Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Planhat Companies Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Planhat Companies 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

A schedule fires, Planhat work gets done.

Fetch companies, group them, draft a digest, approve, post back to Planhat.

Planhat digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch companies

    Planhat

    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

    Planhat

    Queued

Collections and dashboards

Planhat health, counted and refreshed on schedule.

Four metrics, 14 days of records created, and a breakdown by team.

Planhat health

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

Live

Companies

1,284 ↓ 12%

Campaigns

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Companies created

Last 14 days

By team

Share of activity

Success EMEA 34%

Sales AMER 27%

Marketing 21%

Finance 18%

FAQ

Frequently asked questions

How do I connect Planhat to Claude?

It takes two steps. In Elaichi, choose Planhat and paste in a Planhat API key; that is the whole sign-in, with 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. Claude signs you into Elaichi and your Planhat companies, end users, invoices, campaigns and issues are ready to work with.

Does Planhat work with ChatGPT and Cursor as well as Claude?

Yes. Once Planhat 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 Planhat once and every client you use picks it up.

What can an AI agent actually do with my Planhat data?

With Planhat connected, an agent can look up a company and its end users, list open issues, check invoices, and review the campaigns a customer is part of. It can also create and update those records for you, such as adding a new end user or logging an issue after a call. Because Planhat has a large set of actions, short concrete asks like "show me open issues for Acme" work better than long paragraphs.

Does connecting Planhat give the AI everything in my Planhat workspace?

No. Everything an agent does in Planhat runs inside the access of the person who signed in and the Planhat account whose key was connected, so it sees the same companies, invoices and issues that person could already open. Elaichi can narrow that further, for example to reading only, but it can never widen access beyond what Planhat itself allows.

Can my team share one Planhat connection?

Yes. One person connects Planhat in Elaichi and shares the connection with a team, and nobody else ever handles the Planhat API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who updated a company or created an issue, not a shared account.

Can I stop an agent from deleting or changing things in Planhat?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Planhat companies and issues while blocking deletes, or blocking any change to invoices. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.

What happens to a Planhat connection when someone leaves?

When you offboard a person in Elaichi, their access to Planhat through every connected client ends at once. If they had shared a Planhat connection with a team, it keeps working for everyone else on that team. If you want Planhat gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Does the Planhat MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Planhat 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 Planhat?

Yes. Both let Claude, ChatGPT or Cursor use Planhat. 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 Planhat call.

How is Elaichi different from Composio for Planhat?

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

Put Planhat 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.