How do I find a specific game server?

Use the `list_servers` tool with the search parameter. You can filter by server name, game type (e.g. rust, ark), or country code (e.g. US, DE). The results include server name, IP, player count, and rank. For more advanced filtering (min/max players), use the `search_servers` tool.

Can I track a player's activity across different servers?

Yes. Use `list_players` to find the player by name, then `get_player` to view their full profile, and `get_player_sessions` to see their complete session history including which servers they joined, when they connected and disconnected, and for how long.

What games does BattleMetrics support?

BattleMetrics tracks hundreds of multiplayer games including Rust, ARK, Minecraft, CS2, Valheim, DayZ, and many more. Use the `list_games` tool to get the complete, up-to-date catalog of all supported games with their identifiers.

How do I get details about a specific ban?

First use `list_bans` to find the ban and get its numeric ban ID. Then use `get_ban` with that ID to retrieve the complete ban record including the reason, player identifier, expiry date, scope, and issuing administrator.

BattleMetrics MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: BattleMetrics
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="BattleMetrics Specialist",
    goal="Help users interact with BattleMetrics effectively",
    backstory=(
        "You are an expert at leveraging BattleMetrics 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 BattleMetrics "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

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

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 BattleMetrics MCP Server

Empower your AI agent to operate as a real-time intelligence layer over the global gaming server ecosystem with BattleMetrics, the industry-standard platform for game server monitoring. By connecting BattleMetrics to your agent, you transform complex server population analytics, player lookups, and ban auditing into natural conversation. Your agent can instantly search across thousands of tracked game servers, identify specific players, analyze population trends, and review ban records without navigating dashboards.

When paired with CrewAI, BattleMetrics becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call BattleMetrics 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

Server Discovery — Search and filter game servers by name, game, or country. View live player counts, rank, IP address, and detailed metadata.
Player Lookups — Search the global player database by name and retrieve full profiles including identifiers, playtime stats, and linked servers.
Session Tracking — View a player's complete session history showing which servers they played on, join/leave times, and duration.
Population Analytics — Retrieve historical player count data for any server to analyze peak hours, activity trends, and growth patterns.
Ban Auditing — List and review bans from your organization, filter by server, and inspect ban reasons, scope, and expiry.
Leaderboards — Access time-based leaderboards for any server to identify the most active players.
Game Catalog — Browse all games tracked by BattleMetrics and get detailed ecosystem statistics.

The BattleMetrics MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect BattleMetrics to CrewAI via MCP

Follow these steps to integrate the BattleMetrics MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from BattleMetrics

Why Use CrewAI with the BattleMetrics MCP Server

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

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

BattleMetrics + CrewAI Use Cases

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

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

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

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

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

BattleMetrics MCP Tools for CrewAI (12)

These 12 tools become available when you connect BattleMetrics to CrewAI via MCP:

get_ban

Returns the ban reason, banned player identifier, timestamps, expiry date, scope (server-level or organization-wide), and the administrator who issued the ban. Requires appropriate ban:read scope on the API token. Use this after identifying a ban ID from list_bans. Get details for a specific ban

get_game

Returns details such as the game name, the number of tracked servers and players, and game-specific metadata. Use this to get an overview of a game's ecosystem on BattleMetrics. Get details about a specific tracked game

get_player

Returns the player name, associated identifiers (Steam, EOS, etc.), time played statistics, linked servers, and recent activity. Use this after identifying a player ID from list_players or session history. Get detailed profile for a specific player

get_player_sessions

Each session shows which server the player was on, when they joined, when they left, and the session duration. Useful for auditing player activity, tracking playtime, or verifying presence on a specific server. Get session history for a specific player

get_server

Returns the server name, IP address, port, current player count, max players, rank, game details, map, status, and detailed metadata. Use this when the user already has a server ID and wants deep information. Get detailed information about a specific game server

get_server_leaderboard

Returns player names, IDs, and playtime duration. This is useful for identifying the most active or dedicated players on any tracked game server. Use page_number for pagination. Get the time-based leaderboard for a game server

get_server_player_count_history

Useful for analyzing population trends, peak hours, and server activity patterns over a given time range. If start and stop are omitted, the API returns recent history. Use ISO 8601 timestamps for the date range. Get player count history for a game server over time

list_bans

Each ban includes the ban reason, the banned player identifier, timestamps, expiry, and scope (server-level or organization-wide). Requires appropriate ban:read scope on the API token. Use page_number for pagination and optional server_id to filter bans from a specific server. List bans in your BattleMetrics organization

list_games

Returns each game's ID, display name, and metadata. Useful for discovering which games are available for server and player queries, and for getting the correct game identifier to use in server filters. List all games tracked by BattleMetrics

list_players

Use the search parameter to find players by name. Returns player names, IDs, and metadata. Results are paginated — use page_number to navigate. This is a powerful tool for looking up any player across all supported games. Search and list players across all tracked game servers

list_servers

Use the optional search parameter to find servers by name, or filter by game and country. Returns server name, IP, port, player count, rank, and game type. Results are paginated — use page_number to navigate through results. List game servers tracked by BattleMetrics

search_servers

Unlike the basic list_servers tool, this supports granular filtering by server name, game, country, minimum/maximum player count, rank range, and more. Returns matching servers with full metadata including name, IP, port, player count, rank, game type, map, and status. Use this when you need precise filtering to find specific servers. Results are paginated — use page_number to navigate. Search game servers with advanced filters

Example Prompts for BattleMetrics in CrewAI

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

"Show me the most popular Rust servers in the US right now."

"Look up the player 'shroud' and show me their recent session history."

"Show me the player count trend for server ID 12345 over the last 7 days."

Troubleshooting BattleMetrics MCP Server with CrewAI

Common issues when connecting BattleMetrics to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

BattleMetrics + CrewAI FAQ

Common questions about integrating BattleMetrics MCP Server with CrewAI.

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.

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.

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.

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.

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.