Common Room MCP connector
The Common Room connector brings contacts, organizations, activities and signals into Claude, ChatGPT and Cursor through Elaichi, so your team can ask about accounts, update records and submit feedback inside their own Common Room access.
-
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.
5 tools
How to connect
How to connect Common Room to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Common Room once
-
Open Connections, choose Add connection, and pick Common Room.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Common Room. Common Room'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.
Common Room 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.
Common Room 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.
Common Room 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 Common Room 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 Common Room through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Find warm accounts before the call
Ask which organizations have shown fresh signals this week and pull the contacts behind them. Walk into the call knowing who has been active and where.
-
Sales
Catch the record up after a call
Tell the agent what changed on the call and it updates the contact or organization in Common Room. No tab switching, no forgotten notes.
-
Marketing
Build a list for the next campaign
Describe the audience in plain words, such as contacts at mid-size fintech companies who were active last month, and get the matching records from Common Room.
-
Community
Spot members who went quiet
Ask which active members have not shown an activity in thirty days and get a list to reach out to before they drift away.
-
Developer relations
Log a new contributor the moment they appear
When someone new shows up in a forum or repository, create their contact in Common Room from the chat window and attach the organization they belong to.
-
Customer success
Flag feedback from a customer conversation
Paste what a customer told you and submit it as feedback in Common Room, tied to the right contact, so the product team sees it in context.
Try asking
- “Which organizations showed new signals this week?”
- “Update the Acme contact with today's call notes.”
- “Find contacts at fintech companies active in our community this month.”
Compare
Elaichi vs Zapier MCP vs Composio for Common Room
All three can connect Common Room 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 Common Room tools | Allow or restrict single Common Room 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 Common Room 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.
AI tools
Common Room tools for your AI agents
5 tools are ready to call through Elaichi's MCP endpoint the moment you connect Common Room, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Common Room builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Common Room gets you
6 screens from the product, each doing one job for your Common Room account.
The agent
Ask Common Room questions in plain language.
Get answers from live contacts, organizations and activity signals, not a stale export.
- contacts
- organizations
- activities
- feedback
Ask Elaichi to work across your apps.
Which organizations showed new signals this week?
Update the Acme contact with today's call notes.
Find contacts at fintech companies active in our community this month.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects Common Room to every client.
Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
5 Common Room tools, no code to write.
Browse the catalog, list and update records, and submit feedback through one connector.
- Commonroom get catalog
- Commonroom list objects
- Commonroom create object
- Commonroom update object
ElaichiToolsToolboxes
Each team gets its own Common Room toolbox.
Sales, marketing and community work from toolboxes scoped to the work they actually do.
- Sales
- Marketing
- Community
- Developer relations
ElaichiToolboxesShared connections
Share a Common Room connection without sharing credentials.
One person connects, teammates work through it, and nobody else ever sees a secret.
- Sales EMEA
- Sales US
- Marketing
- Community
ElaichiConnectionsAudit log
Every Common Room action lands in the log.
See when, who, what happened and which record, for every call made.
- 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
Schedules start Common Room work end to end.
New signals are fetched, grouped and drafted into a digest a person approves before posting.
Common Room digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch contacts
Common Room
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
Common Room
Queued
Collections and dashboards
Common Room health numbers, computed, never asked for.
Four metrics, a 14 day chart and a team breakdown, refreshed with no model involved.
Common Room health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Organizations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales US 27%
Marketing 21%
Community 18%
FAQ
Frequently asked questions
How do I connect Common Room to Claude?
Open Elaichi, choose Common Room, and sign in to Common Room over OAuth, the same way you would sign in to it in a browser. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Common Room is now available in Claude under your own access.
Does Common Room work with ChatGPT and Cursor as well as Claude?
Yes. Common Room is connected once in Elaichi and reached through the same endpoint, https://api.elaichi.ai/mcp, from Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You do not connect Common Room separately for each client.
What can an AI agent actually do with my Common Room data?
With Common Room connected, an agent can look up contacts, organizations and activities, filter them by what you describe, create a new contact or organization, update an existing one and submit feedback tied to a record. Short, concrete asks work best, such as which organizations showed new signals this week, rather than a long paragraph of instructions.
Does connecting Common Room give the AI everything in my workspace?
No. Every call to Common Room runs as the person who signed in, so the agent sees only the contacts, organizations and activities that person can already see in Common Room. Elaichi can narrow that further with restrictions, and it never widens it beyond what Common Room itself allows.
Can I stop an agent from deleting or changing things in Common Room?
Yes. Restrictions in Elaichi apply per action, so you can allow reading contacts and organizations in Common Room while blocking the ability to create or update them. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to a Common Room connection when someone leaves?
Offboarding a person in Elaichi ends their access to Common Room through every client at once. A Common Room connection they shared keeps working for everyone else on the team. If you want to remove Common Room entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Common Room MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Common Room 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 Common Room?
Yes. Both let Claude, ChatGPT or Cursor use Common Room. 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 Common Room call.
How is Elaichi different from Composio for Common Room?
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 Common Room: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Common Room 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.