How to Use the Circle.so MCP in CrewAI

Q: How do I restrict Circle.so tools in CrewAI?

Import MCPServerHTTP and use the toolfilter parameter. This lets you give one agent access to read comments while hiding administrative functions from the rest of the crew.

Deploy autonomous community management teams. Connect CrewAI to Circle.so to let specialized agents monitor posts and track members together.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Circle.so MCP to CrewAI

Create your Vinkius account to connect Circle.so 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 Circle.so with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Deploy a community moderation crew

Assign a researcher agent to run `list_community_posts` and gather recent activity. One script cannot handle nuance. That agent passes the raw text to an analyst agent trained specifically on your community guidelines. It triggers `list_post_comments` to read the full thread context before deciding if the discussion violates rules. The analyst digs deeper when it spots trouble. The entire process runs autonomously while maintaining shared memory of the incident.

Map out community structures automatically

Call `list_space_groups` to help an onboarding agent understand your top-level architecture. An autonomous system needs to know where to send new users. Then it maps the specific discussion areas using `list_community_spaces`. A dedicated scheduling agent hits `list_community_events` to compile weekly digests. Event coordinators work the same way. It formats the calendar and hands the draft to a publisher agent without requiring your input.

Circle.so MCP Server member analytics

Pull the active roster via `list_community_members` to track engagement. Correlating multiple data points requires specialized roles. Your data agent compares those names against recent activity logs to find people who stopped participating. A manager agent reviews the engagement report and decides which topics are trending by analyzing `list_community_topics`. Hierarchical execution keeps this organized. The crew handles the heavy lifting of community analytics.

Setup guide

Set up Circle.so 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 Circle.so tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Circle.so 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="Circle.so Analyst",
        goal="Access and analyze Circle.so data via MCP.",
        backstory="Expert analyst with direct Circle.so access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Circle.so 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 Circle.so. 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 Circle.so 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 Circle.so MCP in CrewAI

Pass your Vinkius endpoint directly into the mcps array in your Agent definition. CrewAI natively supports the HTTP transport and automatically registers the community management tools.

Yes. You can share the MCP connection across your entire crew. An analyst can read posts while a separate coordinator agent checks the event schedule.

Import MCPServerHTTP and use the tool_filter parameter. This lets you give one agent access to read comments while hiding administrative functions from the rest of the crew.

Agents maintain short-term memory during their execution run. If an agent reads a post in step one, it remembers that context when analyzing comments in step three.

Auth tokens stay completely isolated. Vinkius processes your member lists and admin profile requests inside a temporary container that terminates immediately after the response. Your private community data never touches disk.

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