2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 12 Tools CLI

Claude Code is Anthropic's agentic CLI for terminal-first development. Add BattleMetrics as an MCP server in one command and Claude Code will discover every tool at runtime. ideal for automation pipelines, CI/CD integration, and headless workflows via Vinkius.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install BattleMetrics and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·bash
# Your Vinkius token. get it at cloud.vinkius.com
claude mcp add battlemetrics --transport http "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
BattleMetrics
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.

Claude Code registers BattleMetrics as an MCP server in a single terminal command. Once connected, Claude Code discovers all 12 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where BattleMetrics data drives decisions without human intervention.

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 Claude Code 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 Claude Code via MCP

Follow these steps to integrate the BattleMetrics MCP Server with Claude Code.

01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed

02

Add the MCP Server

Run the command above in your terminal

03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session

04

Start using BattleMetrics

Ask Claude: "Using BattleMetrics, show me...". 12 tools are ready

Why Use Claude Code with the BattleMetrics MCP Server

Claude Code provides unique advantages when paired with BattleMetrics through the Model Context Protocol.

01

Single-command setup: `claude mcp add` registers the server instantly. no config files to edit or applications to restart

02

Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

03

Claude Code runs headlessly, enabling unattended batch processing using BattleMetrics tools in cron jobs or deployment scripts

04

Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

BattleMetrics + Claude Code Use Cases

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

01

CI/CD integration: embed BattleMetrics tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping

02

Headless batch processing: schedule Claude Code to query BattleMetrics nightly and generate reports without human intervention

03

Shell scripting: pipe BattleMetrics outputs into other CLI tools for data transformation, filtering, and aggregation

04

Infrastructure monitoring: run Claude Code in a cron job to query BattleMetrics status endpoints and alert on anomalies

BattleMetrics MCP Tools for Claude Code (12)

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

01

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

02

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

03

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

04

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

05

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

06

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

07

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

08

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

09

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

10

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

11

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

12

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 Claude Code

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

01

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

02

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

03

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

Troubleshooting BattleMetrics MCP Server with Claude Code

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

01

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
02

Connection timeout

Check your internet connection and verify the Edge URL is reachable

BattleMetrics + Claude Code FAQ

Common questions about integrating BattleMetrics MCP Server with Claude Code.

01

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
02

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
03

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

Connect BattleMetrics to Claude Code

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.