MCP server for Path of Exile game data: wiki, economy, and Craft of Exile lookups
Poe-data-mcp - Path of Exile game data is an MCP integration. MCP server for Path of Exile game data: wiki, economy, and Craft of Exile lookups.
The published pypi package is poe-data-mcp, version 0.3.1. Its declared MCP transport is stdio.
The package declares POE_DATA_MCP_CACHE_DIR: Directory for the Craft of Exile data cache. Defaults to the platform user-cache dir (e.g. %LOCALAPPDATA%/poe-data-mcp on Windows, ~/.cache/poe-data-mcp elsewhere)..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 0.3.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related knowledge & memory MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| POE_DATA_MCP_CACHE_DIR | Directory for the Craft of Exile data cache. Defaults to the platform user-cache dir (e.g. %LOCALAPPDATA%/poe-data-mcp on Windows, ~/.cache/poe-data-mcp elsewhere). | Optional |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
A Model Context Protocol (MCP) server implementation for interacting with the Honeybadger API. This server allows AI agents to fetch and analyze error data from your Honeybadger projects.
A Model Context Protocol (MCP) server that provides access to ProPublica's Nonprofit Explorer API for nonprofit organization search and analysis
Open-source bitemporal memory layer for LLM agents — knowledge graph with conflict resolution.
Push any JSON. Your agent gets a live, queryable schema, graph relationships, and semantic search — inferred automatically. No pipeline. No separate stores. No schema to design.