How to Use the Apex Legends MCP in LlamaIndex

Q: How do I index Apex Legends match history inside LlamaIndex?

Use pip install llama-index-tools-mcp and set up the MCP client with the Vinkius URL. Your agent can then run getmatchhistory and index the raw JSON output directly into your vector database.

Q: Can LlamaIndex query Apex Legends server status?

Yes, the agent can call getserverstatus to check game availability. It can index this status to verify if matchmaking issues are due to regional outages before running other queries.

Q: How do I resolve player UIDs for my Apex Legends index in LlamaIndex?

Your agent can use getnametouid or getoriginuid to map player names to unique IDs. Once resolved, you can index these UIDs as metadata to organize player stats in your vector store.

Q: How often should I update the indexed leaderboard data?

Since getleaderboard updates every six hours, you should schedule your indexing pipeline to run at the same frequency. This keeps your vector store updated with the top 500 players without wasting API calls.

Index Apex Legends stats into LlamaIndex to build a searchable, context-rich gaming knowledge base.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Apex Legends MCP to LlamaIndex

Create your Vinkius account to connect Apex Legends to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Apex Legends with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Query Live Apex Legends Data via LlamaIndex RAG

This MCP server exposes `get_player_stats_by_name` to turn live game data into searchable context inside your LlamaIndex vector store. When your agent calls this tool, it pulls active player metrics and indexes them directly. This lets you run semantic queries against live performance data instead of relying on stale, static documents. This integration allows you to combine live API outputs with your custom game strategy guides. Your agent can cross-reference raw player stats with your tactics wiki to generate personalized coaching tips.

Build Searchable Archives of Match History

This MCP server uses `get_match_history` to feed new matches directly into your LlamaIndex document store. Because this tool tracks player telemetry, indexing the results lets you ask complex questions like which weapon loadouts performed best over the weekend. You can also use `manage_legacy_match_history` to pull historical logs and store them in the same index. This creates a unified, queryable history of a player's competitive career that your agent can search instantly.

Index Competitive Ranks and Map Rotations

This MCP server provides `get_map_rotation` and `get_predator_requirements` to keep your RAG application updated with the latest competitive standings. Your agent can fetch map schedules and register the current pool into your index. By indexing these data points, your LlamaIndex agent can answer natural language queries about whether a player has enough points to rank up on the current active map. It bridges the gap between static knowledge and live game states.

Setup guide

Set up Apex Legends MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Apex Legends MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

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

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Apex Legends tools.",
)
response = await agent.run("List recent Apex Legends data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Apex Legends API. 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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Apex Legends now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Apex Legends MCP in LlamaIndex

Use `pip install llama-index-tools-mcp` and set up the MCP client with the Vinkius URL. Your agent can then run `get_match_history` and index the raw JSON output directly into your vector database.

Yes, the agent can call `get_server_status` to check game availability. It can index this status to verify if matchmaking issues are due to regional outages before running other queries.

Your agent can use `get_name_to_uid` or `get_origin_uid` to map player names to unique IDs. Once resolved, you can index these UIDs as metadata to organize player stats in your vector store.

Since `get_leaderboard` updates every six hours, you should schedule your indexing pipeline to run at the same frequency. This keeps your vector store updated with the top 500 players without wasting API calls.

All calls to resolve player names and UIDs are executed in isolated, ephemeral sandboxes. Vinkius never stores or logs the player identifiers or match histories processed during your LlamaIndex queries.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript