Common Room

What the Common Room connector does

The Common Room MCP server lets Claude, ChatGPT or any MCP client interrogate a go-to-market workspace in plain language — research accounts, surface buying signals, browse activity history and build prospect lists of net-new companies — then write contacts, organizations, segments, activities and notes back into it. Five tools, four of them a generic object dispatcher. No free plan exists.

Common Room tools (5)

• commonroom_get_catalog
• commonroom_list_objects
• commonroom_create_object
• commonroom_update_object
• commonroom_submit_feedback

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

• Four tool names hide a CRUD dispatcher. Creation reaches contacts, organizations, segments, activities and notes; updates reach only contacts and organizations. Read the object tables, not the tool count.
• Activities and notes have no documented update or delete path here. An agent that logs a wrong activity onto a person's timeline cannot correct it through this connector.
• Organization updates are narrow — segmentId and customFields only. Names and domains are not updatable on this surface.
• The read catalogue is open-ended. Common Room names contact, organization, activity, segment and tag, then says "and more". The authoritative list comes from commonroom_get_catalog, which requires an authenticated workspace. We did not authenticate, so the read surface is bounded below but not above.
• Segment membership is an update, not a distinct tool, so bulk list-building is a write loop over individual records.
• Upsert means creation can silently modify existing records. A create call matching an existing email, LinkedIn URL or domain updates that record instead. Common Room documents this as deduplication; the effect is that "create" is sometimes "edit".
• Prospector puts third-party contact details in reach. Work emails, personal emails and LinkedIn profiles for people who are not in your workspace and did not supply them to you, plus phone numbers through a premium add-on. Common Room states Prospector may constitute a sale under the CCPA and publishes an opt-out route. This page takes no legal position.
• Common Room's two database figures do not agree — 200M+ contacts in one place, 400M+ profiles in another, both published by Common Room and both fetched 2026-08-19.
• Only four OAuth scopes, all identity scopes. Nothing distinguishes reads from writes. Consent cannot narrow this connector; only your Common Room role can.
• plain is advertised alongside S256 in the PKCE methods on the authorization server. A strict client should insist on S256.
• No free plan. Common Room's published entry tier is 2,500 USD/month billed annually with five seats. MCP carries no separate charge and is included across all plans.
• Acting on Prospector results needs the Prospector add-on, though searching is included on all plans. Prospector credits are metered per tier — 2.5k, 7.5k and 15k on the three published plans.
• Two admin gates exist, at opposite ends. A Common Room admin can disable MCP for the whole instance from Settings, and that page also shows which users connected and with which assistant. Separately, a Claude admin may need to install the connection first.
• Multi-workspace users get their default workspace. Common Room states that if your account belongs to several workspaces the server uses the default one — so an agent may read and write the wrong workspace without saying so.
• commonroom_submit_feedback sends data to the vendor. It does not touch your records, but Common Room does not document what the payload contains.
• No delete tool. Neither source lists one; Common Room documents contact deletion as an in-app action. The connector cannot remove a record it created.
• Custom connectors are not supported inside Projects, per Common Room's documentation.
• Outreach is drafted, never sent. Common Room states sending requires your own email or messaging tool. This is a real restraint and this page credits it — an adjacent prospecting connector in this catalogue can start automated outreach from a tool call.
• We could not verify tool behaviour ourselves. The endpoint returns 401 to anonymous initialize and to anonymous tools/list, so no inputSchema and no readOnlyHint or destructiveHint annotations were readable. No tool was called and no authentication was attempted. Every capability claim here comes from Common Room's documentation, its live OAuth metadata, or Anthropic's listing.
• Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, and none are documented for the connector. The pre-built prompts Common Room documents belong to the plugin.

Frequently asked questions

Sources

• Common Room MCP Server — https://www.commonroom.io/docs/using-common-room/mcp-server/ (last updated 2026-06-19, fetched 2026-08-19; the authoritative source for this page — the five-tool table with descriptions, the field-level create table for contact, organization, segment, activity and note, the update table restricted to contact and organization with their c_ and o_ ID prefixes, the "and more" tail on the readable object types, upsert semantics, prospectorContactId and prospectorCompanyId, the OAuth 2.1 description and per-user token scoping, the statement that writes respect the same permissions as reads with no shared service account, the Settings admin kill-switch, the Claude-admin installation prerequisite, the default-workspace behaviour, the Projects limitation, the client setup steps, and the statement that AI-drafted outreach is drafted in conversation only) · retrieved 2026-06-19
• Claude Connector & Plugin — https://www.commonroom.io/docs/using-common-room/common-room-for-claude-connector-and-plugin/ (last updated 2026-05-14, fetched 2026-08-19; this is the page Anthropic's documentation URL resolves to — the connector-versus-plugin definitions, the read and write capability lists, the SSO/SAML and licence-or-seat requirements, the marketplace URLs for each, the plugin's pre-built call prep, account research, weekly brief and prospecting workflows, and the FAQ confirming both surfaces create and update records) · retrieved 2026-05-14
• Prospector — https://www.commonroom.io/docs/using-common-room/prospector/ (fetched 2026-08-19; profiles and contact details of non-engaged personas at target accounts, work emails, personal emails and LinkedIn profile links, phone numbers via a premium enrichment partnership, the LinkedIn-plus-other-sources origin, the 200M+ contacts and 400M+ profiles figures, search included on all plans against the add-on required to act on results, the 10,000-record bulk cap, and the opt-out route for California, Colorado, Virginia, Connecticut and EU residents) · retrieved 2026-08-19
• Common Room pricing — https://www.commonroom.io/pricing/ (fetched 2026-08-19; no free tier, Essential at 2,500 USD/month billed annually with 5 seats and 100k contacts, Advanced and Enterprise at custom pricing with 15 and 30 seats, Prospector credits of 2.5k/7.5k/15k, RoomieAI research credits of 5k/7.5k/10k, premium phone number enrichment metered at 100/100/200 credits, and the statement that Common Room includes its MCP server across all plans) · retrieved 2026-08-19
• Common Room privacy policy — https://www.commonroom.io/privacy-policy/ (last updated 2026-06-26, fetched 2026-08-19; collection from third-party services and organizations, the personal-data categories collected about non-customers, the disclosure that Prospector may be considered a sale under the CCPA, CCPA opt-out and GDPR complaint rights for EEA, UK and Swiss residents, and access, deletion and portability routes. No MCP-specific or AI-agent-specific clause was found) · retrieved 2026-06-26
• www.commonroom.io/robots.txt (fetched 2026-08-19) — allows all user agents, names a sitemap index, and carries no Content-Signal directives on any axis. www.commonroom.io/llms.txt returns 200 and is a 49 KB machine index of the site including the full documentation tree, which is how both doc pages above were located; llms-full.txt returns 404. Method note: appending .md to a docs URL 301-redirects to a help-centre search rather than serving Markdown, so doc pages were read as HTML · retrieved 2026-08-19
• Live anonymous probe — 2026-08-19: an initialize call to https://mcp.commonroom.io/mcp returns HTTP 401 with a JSON body stating authentication is required, and a www-authenticate header naming the path-append resource_metadata URL — authoritative under RFC 9728. An anonymous tools/list returns the same 401. No tool was called and no authentication was attempted · retrieved 2026-08-19
• Live RFC 9728 protected-resource descriptor — https://mcp.commonroom.io/.well-known/oauth-protected-resource/mcp (fetched 2026-08-19; 211 bytes, 4 scopes_supported — openid, profile, email, offline_access — authorization_servers naming https://login.commonroom.io/, and a resource_name of the bare host). The root form returns a 208-byte 200 differing only in the resource value; the path-insert form under /mcp/ returns a 404 HTML error page · retrieved 2026-08-19
• Live RFC 8414 authorization-server metadata — https://mcp.commonroom.io/.well-known/oauth-authorization-server (fetched 2026-08-19; an Auth0 descriptor issued by login.commonroom.io, with authorization_code, refresh_token, client_credentials, device-code and token-exchange grants, code_challenge_methods_supported carrying both S256 and plain, and present registration_endpoint, revocation_endpoint, jwks_uri and client_id_metadata_document_supported). Only the root path form resolves; path-append and path-insert both 404 · retrieved 2026-08-19
• Anthropic connector directory — https://claude.ai/directory/e56221b4-925f-48bb-9176-6cd6e8fae3c1 (snapshot 2026-08-16; 5 tool names, permissions of "Read and write", no prompt names, partner tier, one category, remote type, streamable-http transport, added 2026-02-13, and an oauth2 probe posture returning 401) · retrieved 2026-08-16
• Common Room support — mailto:support@commonroom.io (listed by Anthropic's directory, not contacted)