How to Use the Mod.io MCP in CrewAI

Q: Can I limit which Mod.io tools a specific CrewAI agent can use?

Yes, you can use CrewAI's toolfilter to restrict access. For instance, you can let your researcher agent use getmods while restricting deletemod to your admin agent.

Q: How does this CrewAI integration protect sensitive mod files?

The MCP transport layer handles getmodfile requests inside a secure, zero-trust sandbox. Your downloaded zip files and developer credentials never touch external servers, keeping your game intellectual property safe.

Deploy specialized agent squads to moderate, curate, and analyze your Mod.io game communities using CrewAI and MCP tools.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Mod.io MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous Mod.io MCP Server Moderation Crews

The `get_mods` tool allows a crew of specialized agents to scan new uploads and police your game's pages. Your CrewAI moderator agent can scan new uploads while a separate analyst agent checks stats. If a file violates guidelines, the moderator agent executes `delete_mod` or flags it for review. The entire operation runs autonomously without requiring manual developer oversight.

Automated Community Curators using CrewAI

The `get_collections` tool lets your curation crew find trending lists and build fresh bundles. One crew member reads player feedback using `get_my_ratings`, while another uses the collections tool to organize them. They collaborate to build fresh bundles, invoking `add_collection` to group high-quality assets. The crew then uses `add_mod` to keep the community hubs active and populated.

Advanced Game Analytics and Reporting

The `get_game_stats` tool lets your analytical crew pull deep metrics to monitor platform health. This Mod.io MCP Server lets CrewAI agents pull deep metrics using this tool along with `get_game` to see how titles are performing. The crew processes these statistics, compares them against historical performance, and drafts summaries. They can even track subscription trends by checking `get_my_subscriptions` over time.

Setup guide

Set up Mod.io 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 Mod.io tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

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

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

You configure the Mod.io MCP Server at the crew level, allowing all agents to share tools like `get_mods` and `get_game` through their collaborative memory system.

Yes, you can use CrewAI's `tool_filter` to restrict access. For instance, you can let your researcher agent use `get_mods` while restricting `delete_mod` to your admin agent.

Your crew can assign a dedicated player-support agent to handle library requests. This agent uses `subscribe_mod` and `unsubscribe_mod` to manage content installations on behalf of authenticated users.

No, the crew shares a single connection token managed by Vinkius. This token handles authentication for all 22 tools, including secure endpoints like `get_my_wallets`.

The MCP transport layer handles `get_mod_file` requests inside a secure, zero-trust sandbox. Your downloaded zip files and developer credentials never touch external servers, keeping your game intellectual property safe.

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