Robin MCP connector
The Robin connector brings desk and room reservations, buildings, and teammates into Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person checks and books space inside their own Robin access with every call logged.
-
How it connects. Connects over OAuth. 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 Robin to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Robin once
-
Open Connections, choose Add connection, and pick Robin.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Robin. Robin's own window opens. Whoever approves it decides what this connection can reach.
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.
Robin 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.
Robin 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.
Robin 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 Robin 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 Robin through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Workplace
Book a desk near the team
Ask for a free desk on the floor where your team sits and reserve it for the days you are in, without opening the Robin map.
-
Executive assistants
Find a room that fits the meeting
Look for a room with enough seats in the right building and book it for the slot already on the calendar.
-
People
Plan an onboarding day around who is in
Check which teammates have desks reserved this week so a new hire's first day lands when the people they need are actually in the office.
-
Office management
See which rooms are reserved today
Pull the day's reservations for a building so catering and cleaning know which rooms will be in use and when.
-
IT
Reserve space for a hardware refresh
Book a room for a few days in the right building and check which desks are free for laptop handoffs.
-
Sales
Set up a room for a customer visit
Look up the building address, find a room that fits the group, and book it for the hours the customer is on site.
Try asking
- “Book me a desk near the design team on Thursday.”
- “Which rooms in the London office are free at 2pm today?”
- “Who from finance has a desk reserved this week?”
Compare
Elaichi vs Zapier MCP vs Composio for Robin
All three can connect Robin 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 Robin tools | Allow or restrict single Robin 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 Robin 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 | $15 per user per month. | 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.
See it in Elaichi
What connecting Robin gets you
5 screens from the product, each doing one job for your Robin account.
The agent
Ask about desks and rooms in plain language.
Check Robin reservations and book a desk or room by typing what you need.
- reservations
- desks
- rooms
- buildings
Ask Elaichi to work across your apps.
Book me a desk near the design team on Thursday.
Which rooms in the London office are free at 2pm today?
Who from finance has a desk reserved this week?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects Robin to every MCP client.
Claude, ChatGPT and Cursor reach Robin through one governed endpoint, no SDK and no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Robin toolbox.
Scope desks and rooms to Workplace, assistants or IT, one toolbox per team.
- Workplace
- Executive assistants
- People
- IT
ElaichiToolboxesShared connections
Share one Robin connection without sharing a credential.
One person connects Robin, teams work through it, and nobody else sees a secret.
- Workplace
- Headquarters
- London office
- Executive assistants
ElaichiConnectionsAudit log
Every Robin booking is logged with a name.
See when a desk or room was reserved, by whom, and for which resource.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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
Monday's reservations become a digest, approved and posted.
A schedule fetches Robin reservations, groups them, drafts a digest, a person approves, it posts back.
Robin digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch reservations
Robin
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
Robin
Queued
Collections and dashboards
Robin occupancy numbers arrive without anyone asking.
Four metrics, fourteen days of reservations, and a split by team, refreshed on schedule, no model.
Robin health
Refreshed 4 minutes ago · every 15 minutes · from the reservations collection
Reservations
1,284 ↓ 12%
Desks
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Reservations created
Last 14 days
By team
Share of activity
Workplace 34%
Headquarters 27%
London office 21%
Executive assistants 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Robin to Claude?
Connect Robin in Elaichi first: you sign in to Robin over OAuth and approve access, with no client ID or secret to generate and no OAuth application to register. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. From that point Claude can check Robin reservations and book desks and rooms as you.
Does Robin work with ChatGPT and Cursor as well as Claude?
Yes. Robin is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. There is nothing extra to set up per client.
What can an AI agent actually do with my Robin data?
Once Robin is connected, an agent can check your reservations, find free desks and rooms in a building, book them for a given time, and look up where teammates are sitting. What is available depends on what your Robin account has set up. Short, concrete asks such as a desk near a named team on a named day work better than long sentences.
Does connecting Robin give the AI access to every building and reservation?
No. Every call to Robin runs as the person who signed in, so the agent sees the buildings, desks, rooms, and reservations that person can already see in Robin and nothing more. Elaichi can narrow that access further with restrictions, and it can never widen it.
Can I stop an agent from booking or cancelling things in Robin?
Yes. Restrictions in Elaichi apply per action, so you can allow an agent to read Robin reservations while blocking it from booking or cancelling. A restricted action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.
What happens to a Robin connection when someone leaves?
Offboarding that person in Elaichi ends their access to Robin through every client at once. A Robin connection they shared keeps working for everyone else on the team. Disconnecting Robin once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the Robin MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Robin 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.
Is Elaichi an alternative to Zapier MCP for Robin?
Yes. Both let Claude, ChatGPT or Cursor use Robin. 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 Robin call.
How is Elaichi different from Composio for Robin?
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 Robin: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Robin 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.