4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Mod.io MCP Server

Bring Modding
to CrewAI

Learn how to connect Mod.io to CrewAI and start using 22 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add CollectionAdd ModDelete ModEdit ModGet Collection ModsGet CollectionsGet GameGet Game StatsGet GamesGet MeGet ModGet Mod FileGet Mod FilesGet ModsGet My PurchasesGet My RatingsGet My SubscriptionsGet My WalletsGet TermsRate ModSubscribe ModUnsubscribe Mod

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Mod.io

What is the Mod.io MCP Server?

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

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.

How it works

  1. Subscribe to this server
  2. Enter your mod.io API Key and Access Token
  3. Start managing your mods from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Gamers — instantly find and subscribe to new mods for your favorite games without leaving your chat interface
  • Mod Creators — manage your mod listings, update summaries, and check performance stats directly from your workspace
  • Community Managers — monitor mod ratings and game statistics to understand community trends and engagement

Built-in capabilities (22)

add_collection

Requires OAuth 2 Access Token. Create a new mod collection

add_mod

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

delete_mod

Requires OAuth 2 Access Token. Delete a mod

edit_mod

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

get_collection_mods

Get mods within a collection

get_collections

Get all mod collections for a game

get_game

Get details for a specific game

get_game_stats

Get statistics for a game

get_games

io platform. Get all games on mod.io

get_me

Requires OAuth 2 Access Token. Get authenticated user details

get_mod

Get details for a specific mod

get_mod_file

Get a specific modfile

get_mod_files

Get all files for a mod

get_mods

Get all mods for a game

get_my_purchases

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

get_my_ratings

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

get_my_subscriptions

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

get_my_wallets

Requires OAuth 2 Access Token. Get user wallets for monetization

get_terms

Get text and links for user consent dialogs

rate_mod

Requires OAuth 2 Access Token. Rate a mod

subscribe_mod

Requires OAuth 2 Access Token. Subscribe to a mod

unsubscribe_mod

Requires OAuth 2 Access Token. Unsubscribe from a mod

Why CrewAI?

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.

  • 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

  • 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

  • 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

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

See it in action

Mod.io in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Mod.io and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Mod.io to CrewAI 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Mod.io in CrewAI

The Mod.io 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 22 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI 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.

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

The Vinkius Advantage

How Vinkius secures Mod.io for CrewAI

Every tool call from CrewAI to the Mod.io MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I see the details of a specific mod using its ID?

Yes! Use the get_mod tool with the game_id and mod_id. Your agent will return full metadata, descriptions, and stats for that specific mod.

02

How do I subscribe to a mod through the AI?

Simply use the subscribe_mod action with the target game and mod IDs. The agent will handle the authentication and add it to your subscription library.

03

Is it possible to check game popularity statistics?

Yes, the get_game_stats tool provides real-time data on game popularity, mod counts, and download metrics for any game on the platform.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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.

Explore More MCP Servers

View all →