About TF2 Wiki
TF2 Wiki is an MCP server for LLM clients that provides live access to the Team Fortress Wiki, including general pages and TF2 weapon, class loadout, cosmetic, and update information. Alongside page search and summaries, it offers structured weapon data and prompts.
Key features
- 01Searches, fetches, and summarizes wiki pages
- 02Lists page sections and recent changes
- 03Retrieves structured weapon stats
- 04Lists class loadouts and event items
- 05Fetches update patch notes
Use cases
- 01Verify weapon stats and class loadouts
- 02Look up cosmetics or event items
- 03Find patch notes for a specific update
- 04Fetch selected sections of a wiki page
MCP support
Exposes live Team Fortress Wiki search and lookup tools, a resource, and prompts to MCP clients over stdio.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEtf2-wiki-mcp
An MCP server that exposes the Team Fortress Wiki to LLM clients (Claude Desktop, Claude Code, Cursor, VS Code) over stdio.
Not affiliated with Valve Corporation or the Team Fortress Wiki contributors. Team Fortress 2 is a trademark of Valve Corporation. This is unofficial fan tooling.
What it does
Gives an LLM live, accurate access to TF2 wiki content so it stops guessing at weapon stats, patch notes, and cosmetic details.
- Generic wiki access — search, fetch pages, get summaries, list recent changes.
- TF2 domain tools — structured weapon stats, class loadouts, cosmetic lookup, event item lists, patch notes.
Tools
| Tool | Purpose |
|---|---|
search_wiki(query, limit) | Full-text search |
get_page(title, format) | Page content as wikitext, plain, or html |
get_page_summary(title) | Lead-section plaintext |
get_page_sections(title) | Section TOC for selective fetching |
get_recent_changes(limit, namespace) | Recently edited pages |
get_weapon_stats(weapon_name) | Parsed weapon infobox → structured stats |
list_class_loadout(class_name) | All weapons in a class's wiki category |
get_cosmetic(name) | Cosmetic item infobox params |
list_event_items(event_name) | Items added in an update/event |
get_patch_notes(update_name) | Patch notes for a specific update |
Plus: resource tf2wiki://main, prompts analyze_loadout and compare_weapons.
Installation
Requires uv (which manages the Python toolchain for you). Once installed, uvx tf2-wiki-mcp will fetch and run the server on demand — no manual clone needed.
Standard config works in most MCP clients:
{
"mcpServers": {
"tf2-wiki-mcp": {
"command": "uvx",
"args": ["tf2-wiki-mcp"],
"env": {}
}
}
}
Claude Desktop
Add the standard config above to claude_desktop_config.json:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Restart Claude Desktop. The TF2 wiki tools appear in the tool picker.
Claude Code
claude mcp add tf2-wiki-mcp -- uvx tf2-wiki-mcp
Codex
Add to ~/.codex/config.toml:
[mcp_servers.tf2-wiki-mcp]
command = "uvx"
args = ["tf2-wiki-mcp"]
See the Codex MCP docs.
Cursor
Or add the standard config to ~/.cursor/mcp.json.
Gemini CLI
Add the standard config to your Gemini CLI settings.json per the Gemini CLI MCP guide.
VS Code
Or via the VS Code CLI:
code --add-mcp '{"name":"tf2-wiki-mcp","command":"uvx","args":["tf2-wiki-mcp"],"env":{}}'
See the VS Code MCP guide for details.
VS Code Insiders
Or via the CLI:
code-insiders --add-mcp '{"name":"tf2-wiki-mcp","command":"uvx","args":["tf2-wiki-mcp"],"env":{}}'
Visual Studio
Or manually:
- Open the GitHub Copilot Chat window.
- Click the tools icon (🛠️) → + Add Server.
- Fill in: Server ID
tf2-wiki-mcp, Typestdio, Commanduvx, Argumentstf2-wiki-mcp. - Save.
See the Visual Studio MCP docs.
GitHub Copilot Coding Agent
{
"mcpServers": {
"tf2-wiki-mcp": {
"command": "uvx",
"args": ["tf2-wiki-mcp"],
"env": {},
"type": "local",
"tools": ["*"]
}
}
}
Add this in repository settings under Copilot → Coding agent. See the Copilot Coding Agent MCP docs.
Development
Run from a local clone instead of PyPI:
git clone https://github.com/yusufaf/tf2-wiki-mcp
cd tf2-wiki-mcp
uv sync --dev
uv run pytest # offline, uses recorded cassettes
uv run pytest --live # also hits the real wiki
To point an MCP client at the local checkout:
{
"mcpServers": {
"tf2-wiki-mcp": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/tf2-wiki-mcp", "tf2-wiki-mcp"]
}
}
}
Licensing & Attribution
Code: MIT (see LICENSE).
Wiki content: Not redistributed. This project contains zero scraped wiki data. All page content is fetched live from wiki.teamfortress.com at the user's request and returned directly to the user's LLM client — the same posture as a browser extension.
Wiki content is © its respective contributors under Valve's Steam Subscriber Agreement (Game Site terms). Users of this tool are responsible for compliance with Valve's terms. Code license ≠ content license: MIT covers this codebase, not the wiki content it fetches.
Requests to the wiki include a descriptive User-Agent (tf2-wiki-mcp/<version> (https://github.com/yusufaf/tf2-wiki-mcp)) per MediaWiki etiquette and respect maxlag/Retry-After responses.
Contributing
Don't check in scraped wiki text. Infobox examples for parser tests are fine (short, fair-use-grade fixtures). Full page dumps are not.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.