Common Room MCP
for LuumenAI
Read your Common Room community data and record changes as approved steps
Connect Common Room and the agent can read your workspace directly from the terminal: which object types exist, what fields they carry, and the contacts, organizations, activities and segments behind them. Changes — a new note, a corrected contact, a segment edit — are previewed first and wait for your approval.
The Common Room MCP toolbox
5 tools: 2 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCommonroom get catalogReports 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…
- ReadCommonroom list objectsReads Common Room records — contacts, organizations, activities, segments and custom objects — as a filtered, sorted, paginated list, or fetches one record by ID.
- WriteCommonroom create objectWrites a new contact, organization, segment, activity, note or tag to Common Room. Approval by default
- WriteCommonroom submit feedbackRecords the user's verdict on results returned by a previous Common Room query. Approval by default
- WriteCommonroom update objectEdits an existing contact, organization, custom-object record or segment, identified by its ID. Approval by default
One prompt, start to finish
What a governed Common Room MCP run looks like inside Luumen.
Questions
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as commonroom create object, commonroom submit feedback, commonroom update object. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Common Room MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Common Room MCP to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.