Common Room for AI agents
Common Room gathers go-to-market community signals, letting an agent read and update records tied to customer and community activity over time. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Common Room.
Check the catalog for an object type
Check the catalog to see what object types and fields are available before querying data.
List matching community records
List objects matching a filter, such as recent signups from a target account.
Submit feedback on a record
Submit feedback on a signal or record to help refine future community insights.
5 Common Room actions, graded by risk.
Every Common Room action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
5Create and change things. Allow, or ask the user first.
- common_room.commonroom_get_catalogCommonroom get catalog
- common_room.commonroom_list_objectsCommonroom list objects
- common_room.commonroom_create_objectCommonroom create object
- common_room.commonroom_update_objectCommonroom update object
- common_room.commonroom_submit_feedbackCommonroom submit feedback
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Common Room in three steps.
- 01Your users connect Common RoomThey sign in to Common Room on Arc0 Connect, under your brand, and approve the access you ask for.
- 02You set the rulesReads run, and writes like “commonroom get catalog” can wait for the user to approve.
- 03Any agent can actYour agent calls Common Room through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('common_room', { read: 'allow', write: 'ask', // commonroom_get_catalog destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Common Room connects.
Common Room runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Common Room through the same endpoint, policies and audit log as every other app.
The same Common Room connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- OAuth 2.0 (MCP)
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Common Room from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Common Room and Arc0, answered.
Can I use Common Room with Claude, ChatGPT or Cursor?
Yes. Connect Common Room to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Common Room actions you allow.
How do users connect Common Room?
Common Room runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Common Room through the same endpoint, policies and audit log as every other app.
Which Common Room actions can my agent take?
5 in total: 0 read, 5 write and 0 destructive, such as “commonroom get catalog”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Common Room?
Yes. Allow read actions and deny writes in the Common Room policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Common Room too?
Yes. The same Common Room connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Common Room into your agent.
Your users connect Common Room once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan