ChartHop MCP connector
The ChartHop connector brings your orgs, people, jobs, groups and job codes into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look up and update headcount records within their own ChartHop access, with every change 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 ChartHop to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect ChartHop once
-
Open Connections, choose Add connection, and pick ChartHop.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a ChartHop API key. One person generates a token in ChartHop 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.
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.
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 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 today. 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.
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.
Use cases
What teams do with ChartHop through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting ChartHop gets you
6 screens from the product, each doing one job for your ChartHop account.
The agent
Ask about people and jobs in plain language.
Answers come from live ChartHop records, not a stale export of the org chart.
- people
- jobs
- groups
- job codes
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 or Cursor
MCP clients
One endpoint brings ChartHop to every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
101 ChartHop tools, ready without writing code.
Orgs, people, jobs, groups and job codes, each with its methods listed in the catalog.
- List all ChartHop orgs
- Get single ChartHop org by ID
- Create a ChartHop org
- Update a ChartHop org by ID
Toolboxes
Every team gets its own ChartHop toolbox.
People Ops, Finance and Recruiting each see only the ChartHop tools their work needs.
- People Ops
- Finance
- Recruiting
- Managers
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.
- People Ops
- Finance
- Recruiting
- Engineering
Audit log
Every ChartHop change is on the record.
Who created a job, who moved a person, when, and on which resource.
- When
- Who
- What happened
- Type
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 drafts the headcount digest for approval.
New ChartHop jobs are fetched, grouped, drafted into a digest, approved, then posted back.
ChartHop digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
ChartHop
Queued
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.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 team, 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 blocking deletes or updates. A restricted action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it.
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 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, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put ChartHop in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
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.