# 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.

Source: https://elaichi.ai/connectors/common-room/

## Facts

| | |
| --- | --- |
| Application | Common Room |
| Category | Sales Intelligence |
| AI tools | 5 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Common Room builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | support@commonroom.io |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Common Room is connected

- 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.

## Connect Common Room in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Common Room.
2. Optionally set Share with, then press Connect.
3. Approve it in Common Room. Common Room's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Common Room tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Common Room MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Common Room to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Common Room tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Common Room through Elaichi

### Find warm accounts before the call

Sales. 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.

### Catch the record up after a call

Sales. Tell the agent what changed on the call and it updates the contact or organization in Common Room. No tab switching, no forgotten notes.

### Build a list for the next campaign

Marketing. 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.

### Spot members who went quiet

Community. Ask which active members have not shown an activity in thirty days and get a list to reach out to before they drift away.

### Log a new contributor the moment they appear

Developer relations. 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.

### Flag feedback from a customer conversation

Customer success. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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 my team share one Common Room connection?

Yes. One person connects Common Room in Elaichi and shares the connection with a team, and nobody else on that team handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every change to a Common Room record.

### 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.

## All 5 Common Room tools

Every tool below is callable through https://api.elaichi.ai/mcp once Common Room is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Commonroom get catalog** (Get). Discover available object types, properties, filters, and sort fields
- **Commonroom list objects** (List). Query and retrieve objects with filtering, sorting, and pagination
- **Commonroom create object** (Create). Create new contacts, organizations, segments, activities, and notes
- **Commonroom update object** (Update). Update existing contacts and organizations by ID
- **Commonroom submit feedback** (Action). Provide feedback on query results to improve response quality
