Bring Community Intelligence
to Claude Desktop
Learn how to connect Common Room to Claude Desktop and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Common Room MCP Server?
Connect your Common Room account to any AI agent and take full control of your community orchestration and B2B relationship intelligence through natural conversation.
What you can do
- Member & Identity Orchestration — List and manage community profiles programmatically, using Person360™ technology to resolve cross-channel identities (Slack, Discord, GitHub, etc.)
- Signal Ingestion — Programmatically ingest custom activity signals from social platforms and internal tools to maintain a high-fidelity record of member interactions
- Audience Segmentation — Access and monitor community segments (Highly Engaged, At Risk, etc.) and tags to understand your community's behavioral health in real-time
- Relationship Intelligence — Retrieve complete directories of community members and manage detailed metadata to perfectly coordinate your go-to-market outreach
- Compliance & Privacy — Execute 'Right to be Forgotten' deletions programmatically and monitor API token status and webhooks directly through your agent
How it works
1. Subscribe to this server
2. Retrieve your API Token from Common Room (Settings > API Tokens)
3. Start managing your community intelligence from Claude, Cursor, or any MCP client
No more manual scrubbing through fragmented social logs. Your AI acts as your dedicated community manager and relationship coordinator.
Who is this for?
- Community Managers — instantly retrieve member profiles and check engagement levels using natural language commands
- DevRel & GTM Teams — monitor social signals across multiple channels and identify high-impact contributors without leaving your workspace
- Operations Leads — automate member provisioning and manage webhook configurations through simple AI queries
Built-in capabilities (12)
Create a new community member
Configure a new webhook
Remove member (GDPR)
Delete a webhook
Get member details
Check API token status
g., Slack post, social interaction) into a members timeline. Report community activity
List community members
g., Highly Engaged, At Risk). List community segments
List community tags
List configured webhooks
Update member profile
Why Claude Desktop?
Claude Desktop is the definitive way to connect Common Room to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Common Room in Claude Desktop
Common Room and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Common Room to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Common Room in Claude Desktop
The Common Room MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Common Room for Claude Desktop
Every tool call from Claude Desktop to the Common Room MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Common Room API Token?
Log in to your account, navigate to Settings > API Tokens, and generate a new Bearer Token for your integration.
What is the Person360™ engine?
Person360™ is Common Room's identity resolution engine that unifies data from multiple platforms into one single member profile.
Can the agent ingest custom social signals?
Yes! The ingest_activity tool allows you to push any user interaction into a member's community timeline programmatically.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.