Common Room

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-08-24. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://www.commonroom.io/docs/using-common-room/mcp-server/ ; community alternative: https://github.com/chris-trag/commonroom-mcp

• https://www.commonroom.io/docs/using-common-room/mcp-server/
• https://github.com/chris-trag/commonroom-mcp

A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.

This list came from a repo the vendor does not own. Those are that author's tools for the vendor's API, not the vendor's own published surface, and the two must not be read as the same thing.

• commonroom_add_activity
  Add a new activity record to Common Room (blog post, webinar, conference talk, etc.)
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_add_user
  Add or update a user profile in Common Room
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_activity_types
  Get all available Common Room activity types (article, webinar, presentation, etc.)
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_api_sources_url
  Get URL for Common Room API sources configuration page
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_api_tokens_url
  Get URL for Common Room API tokens configuration page
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_dashboard_urls
  Get URLs for all Common Room dashboard sections (home, segments, search, contacts, etc.). Requires COMMONROOM_BASE_URL in .env file.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_member_activity_url
  Get URL for individual Common Room member activity page (more detailed than overview)
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_member_url
  Get URL for individual Common Room member page
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_organization_url
  Get URL for individual Common Room organization page
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_segment_url
  Get URL for individual Common Room segment page
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_segments
  Get all Common Room audience segments for targeting and analysis
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_sources_url
  Get URL for Common Room sources configuration page
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_tags
  Get all Common Room tags used for categorizing activities and users
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• commonroom_get_user
  Get Common Room user profile and activity data by email address
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• test_tool
  Test tool to verify MCP connection
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.

Install, as the source shows it:

npm install -g @commonroomio/cli

quoted from https://www.npmjs.com/package/@commonroomio/cli on 2026-09-27, via npm

Packages seen, with the version on 2026-09-27:

• npm: @commonroomio/cli 0.2.0

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.

api_gate, verbatim from the file:

enterprise-only

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

• https://github.com/chris-trag/commonroom-mcp

github.com/common-room tied to the vendor by rule 3, account website commonroom.io has the vendor's domain, confidence strong

The five most recently pushed, on 2026-09-08:

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

• Fetch buyer intent signals
• Monitor social and community mentions

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

This page is the canonical home. The listing below is the same product, counted separately in the source markdown.

What that listing says it does: See the full RESEARCHED entry in 05-signals-intent-abm.md (Common Room is filed there as its canonical home in this directory) - aggregates Slack, Discord, GitHub, product-usage, and third-party intent signals into unified contact/organization profiles.

16 of the 1252 entries are cross listed like this. They are why the entry count is 1252 and the unique product count is 1236. The canonical home is declared in INDEX.md, not chosen by the parser.

• https://www.commonroom.io/docs/using-common-room/mcp-server/
• https://www.commonroom.io/product/mcp-server/
• https://github.com/chris-trag/commonroom-mcp
• https://www.vendr.com/marketplace/common-room
• https://marketbetter.ai/blog/common-room-pricing-breakdown-2026/
• https://glama.ai/mcp/servers?query=common+room

6 source URLs. Raw sources field, verbatim:

https://www.commonroom.io/docs/using-common-room/mcp-server/, https://www.commonroom.io/product/mcp-server/, https://github.com/chris-trag/commonroom-mcp, https://www.vendr.com/marketplace/common-room, https://marketbetter.ai/blog/common-room-pricing-breakdown-2026/, https://glama.ai/mcp/servers?query=common+room

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.