GW1 build compiler: skill data, template code encode/decode, validation, hero roster. Read-only.
GW1 build compiler: skill data, template code encode/decode, validation, hero roster. Read-only. Exposed over MCP by the guild wars 1 build compiler mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
An MCP (Model Context Protocol) server that gives any compatible LLM client (Claude, ChatGPT, Cursor…) reliable, deterministic knowledge of Guild Wars 1 builds: skill data lookup, official template code encoding/decoding, and build validation.
Everything the assistant can do here goes through one of these:
get_skill — full record for one skill (by exact name or template id), with closest-match suggestions on typossearch_skills — filtered search: profession, attribute, campaign, elite, name substringdecode_template — in-game template code → professions, attributes, 8 skills with statsencode_template — named build → validated, official in-game template codevalidate_build — GW1 rule check: one elite max, profession/attribute ownership, primary attributes, duplicatesget_hero — hero record by exact name or GWCA idlist_heroes — hero roster with professions, campaigns and unlock notes, filterable by profession/campaigndecode_pawned_team — paw-ned2 team blobs (PvXwiki team pages) → every bar decodedpnpm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Guild Wars 1 Build Compiler's toolset — get_skill, search_skills, decode_template and 5 more — is a fair guide to whether it matches your workflow. It is maintained by Graphmaxer; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_skill | full record for one skill (by exact name or template id), with closest-match suggestions on typos |
| search_skills | filtered search: profession, attribute, campaign, elite, name substring |
| decode_template | in-game template code → professions, attributes, 8 skills with stats |
| encode_template | named build → validated, official in-game template code |
| validate_build | GW1 rule check: one elite max, profession/attribute ownership, primary attributes, duplicates |
| get_hero | hero record by exact name or GWCA id |
| list_heroes | hero roster with professions, campaigns and unlock notes, filterable by profession/campaign |
| decode_pawned_team | paw-ned2 team blobs (PvXwiki team pages) → every bar decoded |
{
"mcpServers": {
"gw1": {
"command": "npx",
"args": ["-y", "pnpm"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.