Gw2 MCP Server

Gw2 mcp mcp server connects Gw2 MCP to AI assistants that speak the Model Context Protocol. A Model Context Provider (MCP) server for Guild Wars 2 that bridges Large Language Models (LLMs) with Guild Wars 2 data sources.

What Gw2 MCP does

A Model Context Provider (MCP) server for Guild Wars 2 that bridges Large Language Models (LLMs) with Guild Wars 2 data sources.

Key capabilities

• Wiki Search — Search and retrieve content from the Guild Wars 2 wiki
• Wallet Information — Access user wallet and currency data via GW2 API
• Smart Caching — Efficient caching with appropriate TTL for static and dynamic data
• Rate Limiting — Respectful API usage with built-in rate limiting
• Extensible Architecture — Modular design for easy feature additions

Tools it exposes

Once connected, the assistant can call these 4 tools directly:

• account — Required for wallet access
• wallet — Required for currency information
• Linting — The Linting tool exposed by this server
• Formatting — The Formatting tool exposed by this server

Installing the gw2 mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply one environment variable: YOUR_GW2_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Go 1.24 or higher - Guild Wars 2 API key (for wallet functionality)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Gw2 MCP sits in that group, and the shape of its toolset — account, wallet, Linting among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by AlyxPink, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the gw2 mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.