Apex & Division Stats by TRN MCP Server for LlamaIndex 9 tools — connect in under 2 minutes
LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Apex & Division Stats by TRN as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
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 Apex & Division Stats by TRN. "
"You have 9 tools available."
),
)
response = await agent.run(
"What tools are available in Apex & Division Stats by TRN?"
)
print(response)
asyncio.run(main())
* 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 Apex & Division Stats by TRN MCP Server
Transform your AI agent into a professional esports analyst with Apex & Division Stats by TRN, powered by the official Tracker Network API. This server gives your agent real-time access to the TRN database — the same data powering tracker.gg, trusted by millions of competitive gamers worldwide.
LlamaIndex agents combine Apex & Division Stats by TRN tool responses with indexed documents for comprehensive, grounded answers. Connect 9 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
- Player Profiling — Retrieve lifetime stats (K/D, kills, wins, damage, headshots, rank tier) for any Apex Legends or Division 2 player across Origin, PSN, and Xbox
- Legend Breakdown — Analyze per-legend performance to identify a player's main, playstyle, and strongest picks
- Match History — Review recent play sessions with aggregated stats to track performance trends over time
- Global Leaderboards — Access world rankings by stat category (Kills, RankScore, Damage, Level) to benchmark players against the global elite
- PvP Intelligence — Deep-dive into Division 2 Dark Zone and Conflict stats including rogue kills, extractions, and DZ rank
- Cross-Game Search — Find any player across the entire TRN ecosystem by username
The Apex & Division Stats by TRN MCP Server exposes 9 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 Apex & Division Stats by TRN to LlamaIndex via MCP
Follow these steps to integrate the Apex & Division Stats by TRN MCP Server with LlamaIndex.
Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token
Run the agent
Save to agent.py and run: python agent.py
Explore tools
The agent discovers 9 tools from Apex & Division Stats by TRN
Why Use LlamaIndex with the Apex & Division Stats by TRN MCP Server
LlamaIndex provides unique advantages when paired with Apex & Division Stats by TRN through the Model Context Protocol.
Data-first architecture: LlamaIndex agents combine Apex & Division Stats by TRN tool responses with indexed documents for comprehensive, grounded answers
Query pipeline framework lets you chain Apex & Division Stats by TRN tool calls with transformations, filters, and re-rankers in a typed pipeline
Multi-source reasoning: agents can query Apex & Division Stats by TRN, a vector store, and a SQL database in a single turn and synthesize results
Observability integrations show exactly what Apex & Division Stats by TRN tools were called, what data was returned, and how it influenced the final answer
Apex & Division Stats by TRN + LlamaIndex Use Cases
Practical scenarios where LlamaIndex combined with the Apex & Division Stats by TRN MCP Server delivers measurable value.
Hybrid search: combine Apex & Division Stats by TRN real-time data with embedded document indexes for answers that are both current and comprehensive
Data enrichment: query Apex & Division Stats by TRN to augment indexed data with live information before generating user-facing responses
Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Apex & Division Stats by TRN for fresh data
Analytical workflows: chain Apex & Division Stats by TRN queries with LlamaIndex's data connectors to build multi-source analytical reports
Apex & Division Stats by TRN MCP Tools for LlamaIndex (9)
These 9 tools become available when you connect Apex & Division Stats by TRN to LlamaIndex via MCP:
get_apex_game_metadata
Useful as reference data. Get current Apex Legends game metadata
get_apex_leaderboard
) on the specified platform. Get global Apex Legends rankings by stat category
get_apex_legend_breakdown
) — kills, damage, wins per legend. Essential for identifying main legend and playstyle. Get per-legend performance breakdown for an Apex player
get_apex_match_history
Useful for tracking recent performance trends. Get recent match sessions for an Apex player
get_apex_player_profile
Get comprehensive Apex Legends stats for a player
get_division2_match_history
Get recent play sessions for a Division 2 agent
get_division2_player_profile
Get comprehensive stats for a Division 2 agent
get_division2_pvp_stats
Get PvP-specific stats for a Division 2 agent
search_player
Returns matching accounts with platform links and game associations. Search for a player across the Tracker Network ecosystem
Example Prompts for Apex & Division Stats by TRN in LlamaIndex
Ready-to-use prompts you can give your LlamaIndex agent to start working with Apex & Division Stats by TRN immediately.
"Show me the full Apex Legends stats for 'ImperialHal' on Origin."
"Compare the legend stats of two players: 'Player1' and 'Player2' on PSN."
"Who are the top 5 Apex players worldwide by RankScore on PC?"
Troubleshooting Apex & Division Stats by TRN MCP Server with LlamaIndex
Common issues when connecting Apex & Division Stats by TRN to LlamaIndex through the Vinkius, and how to resolve them.
BasicMCPClient not found
pip install llama-index-tools-mcpApex & Division Stats by TRN + LlamaIndex FAQ
Common questions about integrating Apex & Division Stats by TRN MCP Server with LlamaIndex.
How does LlamaIndex connect to MCP servers?
Can I combine MCP tools with vector stores?
Does LlamaIndex support async MCP calls?
Connect Apex & Division Stats by TRN with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Apex & Division Stats by TRN to LlamaIndex
Get your token, paste the configuration, and start using 9 tools in under 2 minutes. No API key management needed.