Sesame MCP connector
Connect Sesame to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can look up employees, departments, offices and job charges and keep them current, with every person working inside their own Sesame access.
- Connects with an API key
- Free 14-day trial
- No credit card
List employees in the Barcelona office with their departments
Working in Sesame with Elaichi
-
List all Sesame info
-
List all Sesame employees
-
Get single Sesame employee by ID
How to connect Sesame to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Sesame 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.
Sesame 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.
Sesame 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.
Sesame 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.
Sesame 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 Sesame 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 Sesame through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Sesame is logged.
-
HR
Catch an employee record up after onboarding
Ask for a new hire's Sesame record and have the department, office and job charge filled in from the offer letter, without opening five screens.
-
People Ops
Answer who sits in which department
Pull the list of Sesame employees for a department or office and get it as a clean table when a manager asks for it.
-
Office management
Keep offices and locations current
When a team moves floors or a new site opens, add or update the Sesame office and location and move the affected employees over in one go.
-
Finance
Check headcount by office before budgeting
Count Sesame employees per office and department to sanity check the headcount plan against what is actually in the system.
-
Managers
Find a team member's details fast
Look up an employee in Sesame by name and get their job charge, department and office without asking HR to dig it out.
-
IT
Create the employee record on day one
Create the Sesame employee when the account request comes in, so the record exists before the laptop is handed over.
Try asking
- “List employees in the Barcelona office with their departments”
- “Update Ana García's job charge to Senior Account Manager”
- “Which Sesame departments have no office assigned yet?”
What connecting Sesame gets you
6 screens from Elaichi, each doing one job for your Sesame account.
Ask Elaichi to work across your apps.
List employees in the Barcelona office with their departments
Update Ana García's job charge to Senior Account Manager
Which Sesame departments have no office assigned yet?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about your people in plain language.
Which employees sit in the Madrid office? Answered from live Sesame records.
Copy the endpoint
AI apps
One endpoint for Sesame in every client.
Claude, ChatGPT, Cursor and Microsoft Copilot reach Sesame through one governed endpoint, no SDK, no shared key.
Tool catalog
297 Sesame tools, no custom code needed.
Employees, departments, offices, locations and job charges, covered without writing a line.
Toolboxes
Every team gets its own Sesame toolbox.
HR, Finance and office managers each see only the Sesame tools their work needs.
Shared connections
Share one Sesame connection, hide the key.
Teammates work through a shared Sesame connection without ever seeing the API key.
Audit log
Know who changed each Sesame record.
Every employee update and department change is logged with who, when and what.
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.
Sesame digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch employees
Sesame
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
Sesame
Queued
Workflows
A schedule starts real Sesame work.
New employees are fetched, grouped by office, drafted into a digest and approved before posting.
Sesame 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
HR Spain 34%
HR LATAM 27%
People Ops 21%
Finance 18%
Collections and dashboards
Sesame headcount numbers, refreshed on schedule.
Employees created over 14 days and a breakdown by team, computed without a model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Sesame
All three can connect Sesame 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 Sesame tools | Allow or restrict single Sesame 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 Sesame 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.
Sesame tools for your AI agents
297 tools are ready to call through Elaichi's MCP endpoint the moment you connect Sesame, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 238 of 297 Sesame tools here. Connect Sesame and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Sesame to Claude?
First, connect Sesame in Elaichi by pasting an API key from your Sesame account, which takes about a minute. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no client ID or secret to generate, and Claude will ask you to sign in to Elaichi as yourself.
Does Sesame work with ChatGPT and Cursor as well as Claude?
Yes. Once Sesame 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 Sesame once and every client picks it up.
What can an AI agent actually do with my Sesame data?
It can list and look up Sesame employees, departments, offices, locations and job charges, create new ones, and update or remove existing ones. Ask for the employees in an office, update a job charge after a promotion, or add a department when a team is formed. Short, concrete asks work better than long paragraphs.
Does connecting Sesame give the AI access to every employee record?
No. Every call to Sesame runs as the person who signed in, so the AI only sees the employees, departments and offices that person already has access to in Sesame. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in Sesame?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Sesame employees while restricting deleting employees, departments or offices. 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 Sesame connection when someone leaves?
Offboarding that person in Elaichi ends their access to Sesame through every client at once. If they shared a Sesame connection, it keeps working for everyone else on the team. Disconnecting Sesame once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent together.
Does the Sesame MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Sesame 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 Sesame?
Yes. Both let Claude, ChatGPT or Cursor use Sesame. 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 Sesame call.
How is Elaichi different from Composio for Sesame?
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 Sesame: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Sesame 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