2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 12 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add BattleMetrics as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to BattleMetrics. "
            "You have 12 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in BattleMetrics?"
    )
    print(response)

asyncio.run(main())
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.

LlamaIndex agents combine BattleMetrics tool responses with indexed documents for comprehensive, grounded answers. Connect 12 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

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 LlamaIndex 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 LlamaIndex via MCP

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

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 12 tools from BattleMetrics

Why Use LlamaIndex with the BattleMetrics MCP Server

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

01

Data-first architecture: LlamaIndex agents combine BattleMetrics tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain BattleMetrics tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query BattleMetrics, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what BattleMetrics tools were called, what data was returned, and how it influenced the final answer

BattleMetrics + LlamaIndex Use Cases

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

01

Hybrid search: combine BattleMetrics real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query BattleMetrics to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying BattleMetrics for fresh data

04

Analytical workflows: chain BattleMetrics queries with LlamaIndex's data connectors to build multi-source analytical reports

BattleMetrics MCP Tools for LlamaIndex (12)

These 12 tools become available when you connect BattleMetrics to LlamaIndex 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 LlamaIndex

Ready-to-use prompts you can give your LlamaIndex 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 LlamaIndex

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

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

BattleMetrics + LlamaIndex FAQ

Common questions about integrating BattleMetrics MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query BattleMetrics tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect BattleMetrics to LlamaIndex

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