ChartHop MCP connector
The ChartHop connector brings your orgs, people, jobs, groups and job codes into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can look up and update headcount records within their own ChartHop access, with every change logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Which jobs in the Engineering group are still open?
Working in ChartHop with Elaichi
-
List all ChartHop orgs
-
Get single ChartHop org by ID
-
List all ChartHop people
How to connect ChartHop to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
ChartHop MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
ChartHop MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
ChartHop MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
ChartHop MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
ChartHop MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect ChartHop to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with ChartHop through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in ChartHop is logged.
-
People Ops
Catch a person's record up after a change
After a promotion or a team move, update the person's title, manager and job in ChartHop from a chat instead of clicking through the profile. The change is recorded against whoever asked for it.
-
Finance
Check open jobs against the headcount plan
List every job in ChartHop, see which are filled and which are still open, and total them by group before the planning review.
-
Recruiting
Open a job the moment it is approved
Create the job in ChartHop with the right job code and group as soon as the requisition clears, so the org chart shows the opening the same day.
-
Managers
Answer who sits where without the chart
Ask which people are in a group, who leads it and which jobs are unfilled, and get the answer from live ChartHop records.
-
Operations
Keep groups current as teams reorganize
Add people to a new group, remove them from the old one, and rename or retire groups in ChartHop that no longer match how the company works.
-
IT
Reconcile people and jobs before provisioning
Pull the list of ChartHop people and their jobs to check against your directory before onboarding and offboarding runs, then fix mismatches in ChartHop directly.
Try asking
- “Which jobs in the Engineering group are still open?”
- “Move Priya Shah to the Customer Success group and update her manager.”
- “Create a job code for Staff Data Engineer.”
What connecting ChartHop gets you
6 screens from Elaichi, each doing one job for your ChartHop account.
Ask Elaichi to work across your apps.
Which jobs in the Engineering group are still open?
Move Priya Shah to the Customer Success group and update her manager.
Create a job code for Staff Data Engineer.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about people and jobs in plain language.
Answers come from live ChartHop records, not a stale export of the org chart.
Copy the endpoint
AI apps
One endpoint brings ChartHop to every client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
101 ChartHop tools, ready without writing code.
Orgs, people, jobs, groups and job codes, each with its methods listed in the catalog.
Toolboxes
Every team gets its own ChartHop toolbox.
People Ops, Finance and Recruiting each see only the ChartHop tools their work needs.
Shared connections
Teammates use ChartHop without seeing the API key.
One person connects, shares with teams, and each member still acts under their own name.
Audit log
Every ChartHop change is on the record.
Who created a job, who moved a person, when, and on which resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
ChartHop digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch people
ChartHop
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
ChartHop
Queued
Workflows
A schedule drafts the headcount digest for approval.
New ChartHop jobs are fetched, grouped, drafted into a digest, approved, then posted back.
ChartHop health
Refreshed 4 minutes ago · every 15 minutes · from the people collection
People
1,284 ↓ 12%
Jobs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
People created
Last 14 days
By team
Share of activity
People Ops 34%
Finance 27%
Recruiting 21%
Engineering 18%
Collections and dashboards
ChartHop headcount numbers, computed without a model.
Four metrics, 14 days of people created, and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for ChartHop
All three can connect ChartHop to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 ChartHop tools | Allow or restrict single ChartHop 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 ChartHop 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 | Free for one person; $15 per user per month on Gold. | 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.
ChartHop tools for your AI agents
101 tools are ready to call through Elaichi's MCP endpoint the moment you connect ChartHop, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect ChartHop to Claude?
Connect ChartHop in Elaichi first: ChartHop connects with an API key, so you paste the key from your ChartHop settings and the connection is live. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, and the whole setup takes a few minutes.
Does ChartHop work with ChatGPT and Cursor as well as Claude?
Yes. Once ChartHop is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect ChartHop once and every client picks it up.
What can an AI agent actually do with my ChartHop data?
An agent can look up people, jobs, groups, orgs and job codes in ChartHop, create new ones, update existing ones, and add or remove people from groups. In practice that means asking who is in a group, opening a job with the right job code, or moving a person to a new team, all from a chat. Short, concrete asks such as "list open jobs in Engineering" work better than long paragraphs.
Does connecting ChartHop give the AI access to everyone's records?
No. Each person signs in to Elaichi as themselves, so an agent working in ChartHop only sees and changes what that person could already see and change. Elaichi can narrow that further with restrictions per role, and it never widens what ChartHop itself allows.
Can I stop an agent from deleting or changing things in ChartHop?
Yes. Restrictions in Elaichi work per action, so you can allow reading people and jobs in ChartHop while restricting deletes or updates. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
What happens to a ChartHop connection when someone leaves?
Offboarding a person in Elaichi ends their access to ChartHop through every client at once. A shared ChartHop connection keeps working for everyone else on the team. If you ever want ChartHop gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the ChartHop MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. ChartHop 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, Microsoft Copilot, 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 ChartHop?
Yes. Both let Claude, ChatGPT or Cursor use ChartHop. 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 ChartHop call.
How is Elaichi different from Composio for ChartHop?
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 ChartHop: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put ChartHop in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot