BattleMetrics MCP for AI. Analyze server performance from pure conversation.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
BattleMetrics MCP gives your agent real-time insight into the global gaming server ecosystem. It lets you check live player counts across thousands of game servers, audit player bans by reason or scope, and track deep session history for specific users.
If you need to analyze population trends or look up detailed player profiles, this is what you use.
What your AI can do
Get ban
Retrieves the full details of a specific ban, including who issued it and when it expires.
Get game
Gets general overview stats and metadata for any tracked game title.
Get player
Returns a detailed profile for a specific user, including their total play time and linked servers.
You can find specific servers by name, country, or minimum player count using advanced search parameters.
Get a user's full profile—identifiers like Steam and EOS, total playtime, and linked servers—from their ID.
Pull time-series data to see how many players a specific server had on any given day or week.
List and inspect every ban recorded, including the reason, scope (server vs. organization), and expiry date.
View a player's entire activity log, showing which servers they joined and when they left.
Ask an AI about this
Waiting for input…
BattleMetrics: 12 Tools for Gaming Metrics
These tools let you query specific data points—from server status checks to advanced population trend analysis—for the entire gaming ecosystem.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using BattleMetrics on VinkiusGet Ban
Retrieves the full details of a specific ban, including who issued it and when it expires.
Get Game
Gets general overview stats and metadata for any tracked game title.
Get Player
Returns a detailed profile for a specific user, including their total play time and...
Get Server
Provides deep info on one specific game server, like its IP address or current rank.
Get Server Leaderboard
Gets the list of most active players based on their total playtime duration for a...
List Bans
Lists all bans in your organization, allowing you to filter by server or check expiry dates.
List Games
Returns a list of every game title tracked by the system.
List Players
Searches and lists players across all supported games using just their name.
List Servers
Lists all tracked game servers, allowing filtering by country or game type for basic...
Get Player Sessions
Shows the full record of which server a player was on, and exactly when they joined...
Search Servers
Searches game servers using advanced criteria like rank range and minimum player...
Get Server Player Count History
Pulls historical data showing how many players were online at a specific server over time.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with BattleMetrics, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by BattleMetrics. 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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Figuring out who played what and when is a total headache.
Right. So, today you have to open one dashboard just for live server status; then switch over to another platform to check player IDs or ban records; after that, you might need to export data into Excel and run pivot tables just to see the average peak population across a month. It's clicks, tabs, copy-pasting—a miserable process.
With this MCP, your agent handles it all in natural language. You ask: 'What was the player count for Server XYZ between last Tuesday and last Friday?' The system runs `get_server_player_count_history`, pulls the data, and gives you a clean answer without ever opening a spreadsheet.
Get detailed analytics with list_players.
Before this MCP, finding out who 'PlayerX' was required knowing their exact Steam ID or game account. You’d search multiple databases separately and hope the IDs matched up—it was a guessing game.
Now, you just run `list_players` by name. The system finds the player across all supported games and returns a single profile with all associated identifiers and play stats. It's that simple.
What your AI can actually do with this
This MCP turns complex data queries about gaming into natural conversation. Instead of jumping through multiple vendor dashboards—checking server status here, then running a separate report on player activity there—your agent handles it all in one chat session. You can instantly search across thousands of tracked game servers to find live metrics like IP address and current rank; you don't need to build custom web scrapers or connect disparate APIs just to get basic stats.
For example, if a community manager needs to verify player activity for moderation, your agent pulls the full session history from multiple connected servers. You can also use it to analyze population trends over weeks, seeing exactly when a server peaked or declined. This kind of deep data visibility—from finding specific players via list_players to reviewing organizational ban records with list_bans—is what makes connecting this MCP through the Vinkius catalog so powerful.
It means your AI agent acts as a central intelligence layer over all your gaming metrics.
019d841c-f6d1-7012-bf4c-a503deffac71 Here's how it actually works
The bottom line is: you talk to your agent, and it handles the API logic required to get the answer from BattleMetrics.
First, you subscribe to the MCP in your preferred client (Cursor or Claude) and enter your BattleMetrics Personal Access Token.
Then, you prompt your agent with a natural language request, like 'Show me all US servers running Rust that have fewer than 10 players.'
Finally, your agent executes the necessary tool calls—like search_servers—and returns a synthesized report containing the filtered data.
Who is this actually for?
Game server admins who spend too much time clicking through dashboards; community managers who need quick player audit logs; and esports analysts who require historical data for trend spotting. If you're tired of piecing together metrics from three different vendor portals, this MCP is built for you.
They use it to monitor live server populations, check if a newly banned player has an active session history, or find the IP details of servers that need maintenance.
They rely on this MCP to review detailed session histories for moderation purposes or use list_bans to confirm if a user's ban was organizational or limited to one server.
They analyze historical player count data using get_server_player_count_history to identify peak times for competition and measure overall community growth patterns.
What Changes When You Connect
You can audit bans instantly. Instead of manually cross-referencing multiple ban logs, calling list_bans and then get_ban gives you the full scope, reason, and expiry date in one flow.
Player tracking gets precise. If a user needs to confirm if someone was on Server X during an incident, get_player_sessions provides a minute-by-minute log, far better than looking at general playtime stats from get_player.
Population analysis is straightforward. Forget exporting data and loading it into Excel; you ask for the player count trend using get_server_player_count_history, and the answer comes back formatted for immediate use.
Server discovery gets granular. Don't just list servers; use search_servers to filter by rank or minimum players, finding exactly what you need without wading through hundreds of results from list_servers.
Efficiency improves across the board. Because this MCP is available via Vinkius, you connect once and your agent can run complex queries involving player lookups (list_players), server checks (get_server), and ban audits seamlessly.
See it in action
Investigating a suspected cheating ring.
The community manager notices suspicious activity. They ask the agent to first run search_servers for all high-traffic servers, then use list_players on potential suspects. Finally, they call get_player_sessions to track which specific game servers the individuals were logged into during the suspect time window.
Planning marketing around a peak gaming period.
The analyst needs data for next quarter's budget. They run list_games to see what titles are popular, then use get_server_player_count_history on the top title to identify precise times when player counts spike, telling them exactly when to push ad campaigns.
Handling a major player complaint about unfair bans.
The administrator uses their agent to call list_bans, narrowing it down by the problematic server ID. They then use get_ban to confirm the exact reason and scope, ensuring they communicate accurate information to the user.
Evaluating a game's long-term health.
A developer needs to know if their title is losing traction. They run get_game for metadata, then use list_servers and search_servers to see the distribution of active servers across different countries and compare that against historical player data.
The honest tradeoffs
Listing all server data at once
Asking the agent simply, 'Show me the status of all game servers.' This floods the response with irrelevant information and is slow because it doesn't filter by need.
Instead, use search_servers to narrow the scope. For example: 'Search for US servers running Rust that have more than 50 players but fewer than 200,'—this directs the query efficiently.
Confusing player search and listing
Trying to find a specific user's ID by just asking, 'Who is X?' This usually returns too many results or general info.
Use list_players with the name parameter. It focuses on finding that user's unique profile across all games, giving you the exact identifiers you need.
Checking ban status without scope
Just asking 'Why was this player banned?' The agent might only give a general message and won't provide the critical details about if it was an organization-wide or server-specific action.
First, use list_bans to find the ban ID, then call get_ban. This two-step process ensures you get the full context: reason, scope, and administrator.
When It Fits, When It Doesn't
Use this MCP if your primary need is deep data visibility into player behavior or server population trends; specifically, if you require historical records (using get_server_player_count_history) or granular audit logs (using get_player_sessions). However, don't use it if you just need to know if a server exists; in that case, simply listing servers via list_servers might suffice. If your goal is advanced filtering based on multiple criteria—like country AND rank range—then always default to the powerful search_servers. Never try to combine general listings with specific lookups without first getting a list of valid game IDs using list_games; otherwise, the queries will fail because the agent won't know which games are even trackable.
Questions you might have
How do I use get_server_player_count_history to see trend data? +
You provide the server ID and a date range (start/stop timestamps). The MCP returns historical player counts, helping you identify peak hours or long-term decline in activity.
What is the difference between list_servers and search_servers? +
Use list_servers for a basic rundown of all tracked servers. Use search_servers when you need precise filtering, like finding only servers in 'France' with a rank greater than 50.
I want to find out if a player was banned; which tool do I use? (list_bans) +
Start by calling list_bans to get an overview of all bans in your organization. Once you have the ban ID, use get_ban to retrieve specific details like the reason and scope.
Can I look up a player's activity on multiple servers? (get_player_sessions) +
Yes. If you provide the player identifier, the MCP uses get_player_sessions to generate a complete timeline of every server they joined and left, helping with moderation audits.
What if I only know a game's name? How do I get stats? (get_game) +
First, use list_games to ensure the game title is recognized. Then, use get_game with that specific ID to pull overall ecosystem metadata and trackable server counts for that title.
How do I use get_server to retrieve detailed metadata for a specific game server? +
It returns everything you need: name, IP address, port, player count, rank, map details, and comprehensive metadata. This function gives deep information about one server ID, which is more granular than just listing servers.
When I use get_player, what kind of associated identifiers do I retrieve for a player? +
You get the player's name along with linked identifiers like Steam or EOS. This allows you to build a comprehensive profile using unique IDs and total playtime statistics.
If I need to identify the most dedicated players, should I use get_server_leaderboard? +
Yes, get_server_leaderboard retrieves player names and their accumulated playtime duration. It is the direct tool for finding out who has been the most active on a specific game server.
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.
We've already built the connector for BattleMetrics. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.