MCP server

A read-only Model Context Protocol (stdio) server over the curated PoE2 data layer. Every tool is read-only; the server loads the static data/poe2/*.json tables at startup and never writes, posts, or touches the game.

Add to Claude Code

Published package (placeholder name, easy to rename):

claude mcp add poe2-open-data -- npx -y @acee/poe2-open-data

From a local checkout:

# from a local checkout (after `npm install && npm run build` in the repo root)
claude mcp add poe2-open-data -- node /absolute/path/to/poe2-open-data/dist/server.js

Or via mcp config JSON

{
  "mcpServers": {
    "poe2-open-data": {
      "command": "node",
      "args": ["/absolute/path/to/poe2-open-data/dist/server.js"]
    }
  }
}

Tools (all read-only)

Tool	Args	Description
`search_items`	`{ query, itemClass?, tag?, limit? }`	Free-text search over base item types, optionally filtered by item class or tag.
`get_item`	`{ name \| id }`	Fetch a single base item type by name or id.
`search_skill_gems`	`{ query, colour?, limit? }`	Search skill gems, optionally filtered by gem colour.
`get_skill_gem`	`{ name \| id }`	Fetch a single skill gem by name or id.
`search_mods`	`{ query, domain?, tag?, limit? }`	Search mods, optionally filtered by domain or spawn tag.
`search_passives`	`{ query, type? }`	Search passive nodes. type ∈ keystone \| notable \| ascendancy.
`get_stat`	`{ id }`	Fetch a single stat by id.
`list_tables`	`{}`	List the curated data tables available to query.
`query_table`	`{ table, where?, limit? }`	Generic read-only query over any curated table.

Prefer plain HTTP?

The same data is available as free, read-only static JSON without MCP — see /data/meta.json and the per-table endpoints linked from the home page.