How to Use the Common Room MCP in CrewAI

Deploy a team of autonomous agents to manage your Common Room community using CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Common Room MCP to CrewAI

Create your Vinkius account to connect Common Room to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Common Room with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run autonomous research crews using this MCP Server

Instead of running a single chat window, CrewAI lets you deploy a team of specialized agents. A Researcher agent can use `get_contact_by_email` to identify a new community member. It then hands that data to an Analyst agent, who runs `search_organizations` to check if the member works for an enterprise prospect. Once the analysis is complete, an Operations agent takes over to update your records. This agent calls `add_contact_to_segment` to place the prospect in an enterprise lead bucket, executing the entire lifecycle without any human intervention.

Monitor and moderate community activity with CrewAI

Keep your community healthy by letting agents monitor member behaviors. A Moderator agent can fetch active cohorts using `list_segments` and inspect individual members using `list_segment_members`. It looks for inactive profiles or anomalous behavior patterns that need attention. When an issue is spotted, a Coordinator agent steps in to inspect the member's profile using `get_contact_tags`. The crew can then decide whether to flag the account or assign them to a different segment for targeted outreach.

Automated Activity Auditing

Auditing your community's engagement levels is tedious. With CrewAI, an Auditor agent can query `list_activity_types` to understand what actions members are taking. It compiles this information alongside data from `get_segment_status` to measure overall workspace health. The agent then collaborates with a Writer agent to draft a weekly summary report. Because the crew has shared memory, they can track changes in organization details over time by comparing current `get_organization_details` results with previous runs.

Setup guide

Set up Common Room MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Common Room tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Common Room Analyst",
    goal="Access and analyze Common Room data via MCP.",
    backstory="Expert analyst with direct Common Room access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Common Room transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Common Room Analyst",
        goal="Access and analyze Common Room data via MCP.",
        backstory="Expert analyst with direct Common Room access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Common Room transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Common Room. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Common Room now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Common Room MCP in CrewAI

You pass your Vinkius endpoint URL directly into the agent's MCP configuration array during initialization. This instantly exposes tools like `search_contacts` to that specific agent, allowing it to query your community database autonomously.

Yes, you can use the setup filters to restrict which tools are exposed to which agents. For example, you can give your Researcher agent access to `get_contact_by_email` while restricting segment modification tools to your Operations agent.

CrewAI agents use shared memory to pass context. When one agent fetches details using `get_organization_details`, the resulting payload is stored in the crew's execution context, making it immediately available to other agents for downstream tasks.

CrewAI has built-in execution limits to prevent infinite loops. If an agent repeatedly calls `list_segments` without progressing, the MCP framework halts the task and raises an exception, protecting your API quota from being wasted.

Vinkius processes all tool execution requests within zero-trust, ephemeral V8 isolates. This means your organization profiles and contact records are never stored on Vinkius servers, maintaining strict compliance with your enterprise data policies.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript