gw2

This GW2 MCP Server bridges a large language model with Guild Wars 2 data sources, exposing tools to search the GW2 wiki, retrieve wallet information, and fetch currency metadata. It is designed to be used by LLM tools (such as Claude Desktop or LM Studio) via standard input/output, enabling the model to issue structured tool calls and receive results that synthesize game data with natural language responses. The server offers a wiki_search tool for knowledge retrieval, a get_wallet tool to access a user's wallet balances (requires a GW2 API key with account scope), and a get_currencies tool to fetch currency details. A dedicated Currency List resource is available at gw2://currencies for quick access to currency metadata. The server implements caching strategies to balance freshness and performance, including long-term caching for static data like wiki content and currency metadata, and shorter caching for dynamic wallet data.

To use the server with your LLM, configure the MCP client in your environment to run the server as shown in the installation section, then interact with the server through the provided tools. For wallet access, you must provide a GW2 API key with the account and wallet permissions. Remember to configure your LM tooling to emit tool requests in the expected JSON shape and to handle the response objects returned by the tools. The server runs via Docker, but the conceptual interaction remains consistent across deployment methods.

Prerequisites:

• Docker installed and running
• Optional: GW2 API key for wallet access

Step-by-step:

1. Ensure Go is not required for this deployment if you plan to use the pre-built Docker image. If you want to build locally, you can skip this step when using Docker:

2. Run the MCP server via Docker (as shown in the example configuration):

# Start the GW2 MCP server container (reduces persistence, removes after stop)
docker run --rm -i alyxpink/gw2-mcp:v1

3. Alternatively, configure your MCP client (Claude LM Studio, etc.) to invoke the server container using the following mcp_config snippet:

{
  "mcpServers": {
    "gw2-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "alyxpink/gw2-mcp:v1"
      ]
    }
  }
}

4. If you prefer to run the server locally (not using Docker), you would need to build from source and run the binary according to the project instructions, but the provided Docker image is the recommended deployment path for MCP integration.

Tips and considerations:

• API keys: For wallet access, obtain a GW2 API key with account and wallet permissions and provide it to the server in your tool calls or environment as required by your setup. Never hard-code keys in client prompts.
• Caching: Static data (currencies, wiki content) is cached long-term, while wallet data is cached for shorter periods. If you notice stale wallet data, verify cache TTL settings and API key validity.
• Rate limiting: The server includes rate limiting to respect GW2 API usage; ensure your LLM’s usage patterns align with these limits to avoid throttling.
• Extensibility: The architecture is modular to allow adding new tools or data sources. If you add features, consider updating the wiki or currency endpoints accordingly.
• Security: Treat the GW2 API key securely and avoid exposing it in logs or prompt-visible channels.