Connect AI agents to your Common Room community intelligence platform to access community data, member engagement signals, and go-to-market insights. Query community activity, identify high-intent members, and automate community-led marketing workflows
DeepSeek Harness (DSH) is DeepSeek's agent harness. Each MCP server is one plugin entry in your project config.
This guide connects Common Room MCP to DeepSeek Harness through MewCP, so DeepSeek Harness can use Common Room MCP's 5 tools, like commonroom_get_catalog, commonroom_list_objects and commonroom_submit_feedback, without your Common Room MCP credentials ever reaching the app.
Common Room MCP signs in through managed OAuth. MewCP stores the token encrypted, refreshes it before it expires and injects it only at call time. Your agent never holds it, so it can never leak it.
More apps
Manage your Google Business Profile, business information and customer engagement. Update listings, publish content, monitor reviews and maintain your local presence across Google services.
Full Google Search Console control for search analytics, sitemaps, sites, and URL inspection, directly from your AI workflows. This MCP server exposes the Google Search Console API for querying search traffic data, managing sitemaps and site properties, and inspecting the indexing status of any URL. It is built for SEO teams monitoring search performance, developers automating sitemap and property management, and analysts pulling search traffic data into reporting pipelines.
Ask your AI to find companies, verify email addresses, and build leads lists with Hunter’s MCP.
Search Apollo's B2B contact and company database, enrich records in bulk, and manage email sequences from your connected Apollo account.
Other clients
Common Room MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact Common Room MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
In your DSH project, or the patch file you mount plugins from.
One plugin instance is one MCP server. Add this to your plugin list.
Tools register as mcp__mewcp__<tool_name>. Sign in when the browser window opens.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
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.
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.
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. When the same segment, tag or custom-field change applies to many records, update them all in one call instead of one call per record. 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.
