Sesame MCP connector
Connect Sesame to Elaichi and Claude, ChatGPT, Cursor 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.
-
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 Sesame to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Sesame once
-
Open Connections, choose Add connection, and pick Sesame.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Sesame API key. One person generates a token in Sesame 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.
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 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.
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.
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.
Use cases
What teams do with Sesame through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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?”
AI tools
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.
See it in Elaichi
What connecting Sesame gets you
6 screens from the product, each doing one job for your Sesame account.
The agent
Ask about your people in plain language.
Which employees sit in the Madrid office? Answered from live Sesame records.
- employees
- departments
- offices
- job charges
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 or Cursor
MCP clients
One endpoint for Sesame in every client.
Claude, ChatGPT and Cursor reach Sesame through one governed endpoint, no SDK, no shared key.
Copy the endpoint
Tool catalog
297 Sesame tools, no custom code needed.
Employees, departments, offices, locations and job charges, covered without writing a line.
- List all Sesame info
- List all Sesame employees
- Get single Sesame employee by ID
- Create a Sesame employee
Toolboxes
Every team gets its own Sesame toolbox.
HR, Finance and office managers each see only the Sesame tools their work needs.
- HR
- People Ops
- Office management
- Finance
Shared connections
Share one Sesame connection, hide the key.
Teammates work through a shared Sesame connection without ever seeing the API key.
- HR Spain
- HR LATAM
- People Ops
- Finance
Audit log
Know who changed each Sesame record.
Every employee update and department change is logged with who, when and what.
- 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 starts real Sesame work.
New employees are fetched, grouped by office, drafted into a digest and approved before posting.
Sesame digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Sesame
Queued
Collections and dashboards
Sesame headcount numbers, refreshed on schedule.
Employees created over 14 days and a breakdown by team, computed without a model.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 blocking deleting employees, departments or offices. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.
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 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, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put Sesame 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.