Skip to content

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.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which organizations showed new signals this week?

Working in Common Room with Elaichi

  • Commonroom get catalog
  • Commonroom list objects
  • Commonroom create object
Ask anything…
Governance / Audit log Last 24 hours
Common Room Commonroom create object Emily Carter · Claude · 9:41 AM Done
Common Room Commonroom list objects Emily Carter · Claude · 9:41 AM Done
Common Room Commonroom get catalog Emily Carter · Claude · 9:41 AM Done
Common Room Commonroom update object Megan Brooks · ChatGPT · 9:38 AM Done
Common Room Commonroom submit feedback Ryan Hayes · Cursor · 9:35 AM Done

How to connect Common Room to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Common Room MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

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

Common Room MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Common Room MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Common Room MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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 Common Room to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Common Room through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Common Room is logged.

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

See all 5 Common Room tools →

What connecting Common Room gets you

6 screens from Elaichi, each doing one job for your Common Room account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask Common Room questions in plain language.

Get answers from live contacts, organizations and activity signals, not a stale export.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint connects Common Room to every client.

Claude, ChatGPT, Cursor and Microsoft Copilot share one governed endpoint, with no SDK and no shared key.

ElaichiTools
Tool Action Description
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

Tool catalog

5 Common Room tools, no code to write.

Browse the catalog, list and update records, and submit feedback through one connector.

ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Common Room · accounts and signals

Common Room starter 18 Mar 4, 2026

Marketing toolbox

Common Room · segments and campaigns

— 9 Mar 2, 2026

Community toolbox

Common Room · members and activities

— 24 Feb 27, 2026

Developer relations toolbox

Common Room · contributors and activity

Common Room starter 6 Feb 19, 2026

Customer success toolbox

Common Room · accounts and feedback

— 31 Jan 30, 2026

Revenue operations toolbox

Common Room · records and data quality

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Common Room toolbox.

Sales, marketing and community work from toolboxes scoped to the work they actually do.

ElaichiConnections
Connection Scope Status Access
CO

Common Room (Sales EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
CO

Common Room (Sales US)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
CO

Common Room (Marketing)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
CO

Common Room (Community)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
CO

Common Room (Developer relations)

Connected by Ryan Hayes

Personal • Active Not shared
CO

Common Room (Customer success)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share a Common Room connection without sharing credentials.

One person connects, teammates work through it, and nobody else ever sees a secret.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Common Room Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Common Room Contacts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Common Room Contacts List Toolbox

Audit log

Every Common Room action lands in the log.

See when, who, what happened and which record, for every call made.

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.

Common Room digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch contacts

    Common Room

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Common Room

    Queued

Workflows

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 health

Refreshed 4 minutes ago · every 15 minutes · from the contacts collection

Live

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%

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.

Why connect Common Room's MCP server through Elaichi

Common Room builds and runs this MCP server. Elaichi sits in front of it, so Common Room's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Common Room's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Common Room's tools at the same Elaichi address as every other connected app. Nobody adds Common Room's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Common Room sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Common Room's server. By default, a tool Common Room does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Common Room

    Common Room builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Common Room team.

    [email protected]

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Common Room, by what to check
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 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.

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.

Questions, answered

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, Microsoft Copilot, 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 restricting the ability to create or update them. 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 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, Microsoft Copilot 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, 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 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 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