How to Use the Faceit MCP in LlamaIndex

Q: How do I index Faceit leaderboard data into LlamaIndex?

You query gethubleaderboard to retrieve player rankings and ELO, then use LlamaIndex to ingest those records as document nodes. This creates a searchable, vector-indexed leaderboard that your agent can query semantically.

Q: How do I configure LlamaIndex to search Faceit matches?

You register gethubmatches as a tool within the LlamaIndex McpToolSpec wrapper. The query engine then routes natural language questions about ongoing matches directly to the active hub endpoint.

Q: Does LlamaIndex expose my Faceit match stats to third parties?

No, your match stats retrieved via getmatchstats are processed locally within your LlamaIndex pipeline and the secure Vinkius sandbox. Your competitive data remains private and is never used to train public models.

Index raw Faceit player stats and match histories directly into LlamaIndex vector stores for hallucination-free esports RAG.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Faceit MCP to LlamaIndex

Create your Vinkius account to connect Faceit 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 Faceit with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Index Faceit player profiles with LlamaIndex RAG

Turn raw player data into searchable knowledge bases by querying `get_player` and indexing the returned Steam IDs, ELO ratings, and levels. Your LlamaIndex agent queries this index to answer questions about player backgrounds without calling the API repeatedly. Integrate `get_player_bans` to automatically append ban histories and durations to your vector store. This ensures your gaming assistant makes decisions grounded in verified safety data, rather than guessing player integrity.

Build tournament indexes using this MCP Server

This MCP Server allows LlamaIndex to query `search_tournaments` and build a local index of active prize pools, start times, and skill requirements. Your agent searches this index semantically to match players with tournaments they qualify for. It ingests hub details via `get_hub` to keep your knowledge base updated with the latest competitive rules and organizer settings. You get a self-updating directory of competitive hubs that your users can query naturally.

Query historical match stats in LlamaIndex

Feed historical match results into your index by calling `get_player_history` for specific game IDs. LlamaIndex parses the ELO changes and match outcomes, building a chronological performance map for any player. Combine this history with deep match telemetry using `get_match_stats` to index specific player metrics like headshot percentages and average kills. Your RAG pipeline can then identify performance trends over time, providing deep tactical insights.

Setup guide

Set up Faceit 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 Faceit 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 Faceit tools.",
)
response = await agent.run("List recent Faceit 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 Faceit. 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 Faceit 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 Faceit MCP in LlamaIndex

You query `get_hub_leaderboard` to retrieve player rankings and ELO, then use LlamaIndex to ingest those records as document nodes. This creates a searchable, vector-indexed leaderboard that your agent can query semantically.

Yes, this MCP Server grounds your LlamaIndex queries in real-time data from tools like `get_player_stats`. Instead of guessing a player's win rate, the agent pulls the exact metrics directly from the platform.

You register `get_hub_matches` as a tool within the LlamaIndex McpToolSpec wrapper. The query engine then routes natural language questions about ongoing matches directly to the active hub endpoint.

Yes, you can structure separate index agents for player profiles and match statistics. LlamaIndex uses tools like `get_match` to fetch specific game details, resolving queries across both indexes to build a complete match summary.

No, your match stats retrieved via `get_match_stats` are processed locally within your LlamaIndex pipeline and the secure Vinkius sandbox. Your competitive data remains private and is never used to train public models.

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