4,000+ servers built on vurb.ts
Vinkius

Mod.io MCP Server for CrewAIGive CrewAI instant access to 22 tools to Add Collection, Add Mod, Delete Mod, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to Mod.io through Vinkius, pass the Edge URL in the `mcps` parameter and every Mod.io tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The Mod.io MCP Server for CrewAI is a standout in the Developer Tools category — giving your AI agent 22 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Mod.io Specialist",
    goal="Help users interact with Mod.io effectively",
    backstory=(
        "You are an expert at leveraging Mod.io tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Mod.io "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 22 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Mod.io
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Mod.io MCP Server

Connect your mod.io account to any AI agent to manage your gaming library and modding workflows through natural conversation.

When paired with CrewAI, Mod.io becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Mod.io tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Game Discovery — Browse all games on the platform using get_games and fetch detailed stats and metadata for specific titles with get_game_stats.
  • Mod Management — Search for mods using get_mods, view detailed descriptions with get_mod, and manage your own mod profiles including adding, editing, or deleting entries.
  • User Subscriptions — Subscribe or unsubscribe from mods using subscribe_mod and unsubscribe_mod, rate content with rate_mod, and track your personal collections.
  • Account Insights — Access your profile with get_me, check your wallet information via get_wallets, and view purchased content directly through the API.

The Mod.io MCP Server exposes 22 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 22 Mod.io tools available for CrewAI

When CrewAI connects to Mod.io through Vinkius, your AI agent gets direct access to every tool listed below — spanning modding, user-generated-content, game-api, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add collection on Mod.io

Requires OAuth 2 Access Token. Create a new mod collection

add

Add mod on Mod.io

Requires OAuth 2 Access Token. Add a new mod to a game

delete

Delete mod on Mod.io

Requires OAuth 2 Access Token. Delete a mod

edit

Edit mod on Mod.io

Requires OAuth 2 Access Token. Edit details of an existing mod

get

Get collection mods on Mod.io

Get mods within a collection

get

Get collections on Mod.io

Get all mod collections for a game

get

Get game on Mod.io

Get details for a specific game

get

Get game stats on Mod.io

Get statistics for a game

get

Get games on Mod.io

io platform. Get all games on mod.io

get

Get me on Mod.io

Requires OAuth 2 Access Token. Get authenticated user details

get

Get mod on Mod.io

Get details for a specific mod

get

Get mod file on Mod.io

Get a specific modfile

get

Get mod files on Mod.io

Get all files for a mod

get

Get mods on Mod.io

Get all mods for a game

get

Get my purchases on Mod.io

Requires OAuth 2 Access Token. Get mods purchased by the user

get

Get my ratings on Mod.io

Requires OAuth 2 Access Token. Get ratings submitted by the user

get

Get my subscriptions on Mod.io

Requires OAuth 2 Access Token. Get mods the user is subscribed to

get

Get my wallets on Mod.io

Requires OAuth 2 Access Token. Get user wallets for monetization

get

Get terms on Mod.io

Get text and links for user consent dialogs

rate

Rate mod on Mod.io

Requires OAuth 2 Access Token. Rate a mod

subscribe

Subscribe mod on Mod.io

Requires OAuth 2 Access Token. Subscribe to a mod

unsubscribe

Unsubscribe mod on Mod.io

Requires OAuth 2 Access Token. Unsubscribe from a mod

Connect Mod.io to CrewAI via MCP

Follow these steps to wire Mod.io into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 22 tools from Mod.io

Why Use CrewAI with the Mod.io MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Mod.io through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Mod.io + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Mod.io MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Mod.io for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Mod.io, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Mod.io tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Mod.io against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Mod.io in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Mod.io immediately.

01

"List all games available on mod.io."

02

"Show me the mods for game ID 123."

03

"Rate mod 789 for game 123 as positive."

Troubleshooting Mod.io MCP Server with CrewAI

Common issues when connecting Mod.io to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Mod.io + CrewAI FAQ

Common questions about integrating Mod.io MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Explore More MCP Servers

View all →