Common Room MCP in Claude: your accounts and signals, plus Linkeddit's competitor data

Common Room's documentation lists five tools. commonroom_get_catalog lists the object types, properties, filters and sort fields. commonroom_list_objects queries Contacts, Organizations, Activities, Segments and Tags with filtering, sorting and cursor pagination. commonroom_create_object creates contacts, organizations, segments, activities and notes. commonroom_update_object changes existing contacts and organizations, and commonroom_submit_feedback sends feedback on a result.

Access is per person. Common Room's docs say each user signs in with their own account through OAuth 2.1, with no shared token, and that Claude can read or write only what that account can. An admin can turn MCP off for the whole instance under Settings. The Agent Index lists the connector as read and write, with 5 tools: 2 reads and 3 writes.

Two behaviors matter for safety. Creating a contact or organization is an upsert, matched on email, LinkedIn URL or domain, so an existing record is updated rather than duplicated. And Common Room does not send outreach: its docs say drafts must go through a separate email or messaging tool.

Install the Common Room connector from Claude's connector directory and sign in. Common Room's own steps are to open Claude's settings, go to Connectors and then Manage, install the connector and complete the OAuth authorization. If you belong to more than one workspace, the docs say the default workspace is used unless a RoomID is specified, so confirm which workspace Claude is reading before it writes anything.

Claude Code works the same way through the endpoint https://mcp.commonroom.io/mcp. Add the Linkeddit connector at https://mcp.linkeddit.com/mcp beside it, and Claude can use both in one session. Linkeddit comes with the $60 a month plan.

Common Room describes its connector as buyer intelligence from your own workspace: account and contact signals, CRM fields synced into Common Room, enrichment, product usage and engagement history. Its launch post says "Claude becomes the interface. Common Room powers the intelligence behind it." All of it is about the people and accounts you already know.

Linkeddit covers the market around them. Compete records competitor moves from blogs, changelogs and monitored pages, each with a priority. On Linkeddit's test project, plausible.io, the latest competitor signals are dated for the week of 2026-10-26: Umami published a roadmap post and a preview of its v3 release, and Simple Analytics published a post on an EU plan to move consent into the browser. Answer Radar records where the five answer engines name a competitor instead of you.

A founder in competitive intelligence described why neither is enough alone. "The problem was never a lack of information. It was a lack of decision ownership," wrote a competitive intelligence founder on Reddit. Putting a dated competitor move next to an account that cares about it gives someone a reason to act.

Ask Claude to read this week's moves from Linkeddit with compete_signals_get, then to find the accounts that would care using commonroom_list_objects, for example Organizations in a segment you name. Claude can save the result as a Common Room segment with commonroom_create_object, or add a note to a named contact's timeline. Common Room has no alert tool in its MCP list, so the alert is a record you create, not a push notification.

Keep the write small and reviewed. A note needs a contactId, and an activity needs a contactId and an activityType, so Claude must name the contact before it writes. Have it show the exact text first. Common Room's updates are limited to listed contact and organization fields, so a competitor move belongs in a note or segment name, not in a field you rely on.

Competitor research starts on Linkeddit's side. On the test project, search_competitors_get covers 358 competing domains from 59 checked keywords. matomo.org is in the Google top 10 on 11 of them and was cited 23 times across the engines in the latest finished run. Claude can then look in Common Room for the accounts in your workspace that already engage with those competitors' category, using the filters commonroom_get_catalog reports.

For AI citation outreach, answer_gaps_get lists the buying questions where an engine recommended someone else. The top open gap on the test project is "Not represented for: 'Umami vs Matomo for self-hosted analytics'", with a confidence of 1. Reading the cited pages with answer_sources_fetch spends credits, so Linkeddit returns an estimate first and Claude waits for your yes. Common Room then holds the contacts you already know, and Claude drafts outreach in the chat without sending it.

Check the workspace, the record and the text. The connector can create and update records inside your CRM-adjacent workspace, and the docs describe no delete tool, so a wrong note stays until a person removes it in Common Room. Ask Claude to show every create or update call before it makes it, and to say how many records each call touches.

Independent reviewers have flagged limits worth knowing. The agentman.ai listing, which did not sign in or call any tool, notes that no OAuth scope separates read access from write access, and that Common Room's Prospector exposes contact details for people outside your workspace. Read your own workspace permissions before you let Claude write.