Shapes MCP connector
The Shapes connector brings your people data, headcount, attrition risk and compensation, to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so each person can ask questions in plain language within their own Shapes permissions.
- Connects over OAuth
- Free 14-day trial
- No credit card
What is our current headcount by department?
Working in Shapes with Elaichi
-
Looked in Shapes
How to connect Shapes to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Shapes 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.
Shapes 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.
Shapes 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.
Shapes 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.
Shapes 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 Shapes 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 Shapes through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Shapes is logged.
-
People
Answer a headcount question before the meeting
Ask how many people sit in each department in Shapes, how that changed this quarter, and where the open roles are. The answer comes from the live record, not from a spreadsheet exported last month.
-
Finance
Check compensation gaps across a department
Ask Shapes where pay sits outside the band for a level or location and get the figures back before the budget review, limited to the compensation you are already allowed to see.
-
Managers
Spot attrition risk on your team
Ask which people on your team Shapes flags as attrition risks and why, so the conversation happens before the resignation letter does.
-
Leadership
Pull a headcount trend for the board deck
Ask for headcount by region over the last four quarters and have the numbers summarized in plain language, ready to paste into the deck.
-
Recruiting
Find where the organization is thinly staffed
Ask Shapes which teams are under their planned headcount and which roles have stayed open longest, so hiring effort goes where it is needed.
-
People analytics
Compare pay across levels and locations
Ask Shapes how compensation compares between two offices or two levels and get the comparison back in a sentence or a table, inside your Shapes permissions.
Try asking
- “What is our current headcount by department?”
- “Which teams show the highest attrition risk this quarter?”
- “Show compensation gaps between levels in Engineering.”
What connecting Shapes gets you
5 screens from Elaichi, each doing one job for your Shapes account.
Ask Elaichi to work across your apps.
What is our current headcount by department?
Which teams show the highest attrition risk this quarter?
Show compensation gaps between levels in Engineering.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about headcount and get a live answer.
Type a plain question and get figures from the employee records in Shapes.
Copy the endpoint
AI apps
One Shapes endpoint for every AI client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Toolboxes
Each team gets its own Shapes toolbox.
People, Finance and managers each work from a toolbox scoped to their job.
Shared connections
Teammates use Shapes without touching a credential.
One person connects Shapes, shares it with a team, and the log still names each user.
Audit log
Every Shapes question is logged with a name.
See when, who, what happened and which employee record was touched, in one place.
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.
Shapes digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch employees
Shapes
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
Shapes
Queued
Workflows
A schedule drafts the digest, a person approves.
Headcount records are fetched from Shapes, grouped, summarized and posted back after sign-off.
Shapes health
Refreshed 4 minutes ago · every 15 minutes · from the employees collection
Employees
1,284 ↓ 12%
Departments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Employees created
Last 14 days
By team
Share of activity
People team 34%
Finance 27%
Leadership 21%
EMEA 18%
Collections and dashboards
Shapes headcount numbers, computed without a model.
Four metrics, a 14 day chart and a team breakdown, refreshed on a schedule.
Why connect Shapes' MCP server through Elaichi
Shapes builds and runs this MCP server. Elaichi sits in front of it, so Shapes' tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Shapes' server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Shapes' tools at the same Elaichi address as every other connected app. Nobody adds Shapes' server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Shapes sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Shapes' server. By default, a tool Shapes does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Shapes
Shapes builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Shapes team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Shapes
All three can connect Shapes 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 Shapes tools | Allow or restrict single Shapes 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 Shapes 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.
Questions, answered
How do I connect Shapes to Claude?
First, connect Shapes in Elaichi: choose Shapes from the catalog, sign in to Shapes in the browser window that opens and approve access. There is no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on your Shapes people data is available in the conversation.
Does Shapes work with ChatGPT and Cursor as well as Claude?
Yes. Once Shapes 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 Shapes once and every client picks it up.
What can an AI agent actually do with my Shapes data?
It can answer questions about the people data you already have in Shapes: headcount by department or region, who is flagged as an attrition risk, and where compensation falls outside a band. What it can reach depends on what your Shapes account has set up and on your own Shapes permissions. Short, concrete asks such as "headcount in Sales by country" work better than long paragraphs.
Does connecting Shapes give the AI access to everyone's records and pay?
No. Every call to Shapes runs as the person who signed in, so the AI sees only the employees, departments and compensation that person can already see in Shapes. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Shapes allows.
Can I stop an agent from deleting or changing things in Shapes?
Yes. Restrictions in Elaichi apply per action, so you can allow questions about Shapes people data while restricting anything that would change a record. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Shapes connection when someone leaves?
Offboarding a person in Elaichi ends their access to Shapes through every client at once, with no separate steps in Claude, ChatGPT, Cursor or Microsoft Copilot. If they connected a shared Shapes account, that connection keeps working for everyone else on the team. Disconnecting Shapes once in Elaichi removes it from every client.
Does the Shapes MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Shapes 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 Shapes?
Yes. Both let Claude, ChatGPT or Cursor use Shapes. 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 Shapes call.
How is Elaichi different from Composio for Shapes?
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 Shapes: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Shapes 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