Common Room MCP connects agents to an authorized Common Room instance for catalog and go-to-market community intelligence workflows.
Writes a new contact, organization, segment, activity, note or tag to Common Room. Contacts and organizations are upserts, so this both creates and merges into an existing record; use commonroom_update_object instead when editing a record you have already identified. Look up the IDs and existing values it needs with commonroom_list_objects, and the writable fields for each type with commonroom_get_catalog.
Reports which object types this workspace exposes and, for each, the fields it can be filtered by, the properties it can return, the fields it can be sorted by, and the other objects it is associated with. Call it before commonroom_list_objects, commonroom_create_object or commonroom_update_object: field names vary by workspace, so building a filter or a write from guessed names fails.
Reads Common Room records — contacts, organizations, activities, segments and custom objects — as a filtered, sorted, paginated list, or fetches one record by ID. Call commonroom_get_catalog first: it reports which object types exist and which fields each one can be filtered, sorted and returned by. Also use this tool to look up the values other filters expect, such as role names, Bombora topics and location IDs. Use commonroom_create_object or commonroom_update_object to write records; this tool only reads.
Records the user's verdict on results returned by a previous Common Room query. Call it after presenting data, when the user says the results were helpful, says they were wrong or incomplete, or comments on the data quality. It stores feedback only — it neither re-runs the query nor changes any record.
Edits an existing contact, organization, custom-object record or segment, identified by its ID. Every change is a partial update: omitted fields keep their current values and tag changes apply only to the tags listed. Use commonroom_create_object when the record may not exist yet, since that upserts contacts and organizations; use commonroom_list_objects to find the ID to pass here and commonroom_get_catalog for which fields are mutable.
The Common Room MCP integration connects your Dench AI CRM directly to Common Room MCP, so agents can read and act on your Common Room MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
5 actions are available for agents to invoke on your behalf. Every call runs through Common Room MCP's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Common Room MCP and click Connect — you'll authorize access through Common Room MCP's own sign-in flow. No API keys or code required.
Ask an agent to use Common Room MCP in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Common Room MCP integration connects your AI CRM to Common Room MCP, so AI agents can work with your Common Room MCP data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Common Room MCP integration currently exposes 5 actions, including Commonroom create object, Commonroom get catalog, Commonroom list objects, Commonroom submit feedback, and Commonroom update object. Agents invoke them on your behalf from chat or from automations.
No. You connect Common Room MCP from your Dench workspace using Common Room MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Common Room MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Common Room MCP connection from your workspace settings at any time.