How do I use pob-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@pob-mcp find me a cheap starter build for Delirium league" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

PoB MCP Suite

This monorepo contains the complete Path of Building MCP delivery chain:

Path	Responsibility
`vendor/PathOfBuilding`	Vendored `api-stdio` Path of Building fork used by the Lua bridge.
`packages/pob-mcp`	TypeScript MCP server and Docker runtime source.
`packages/pob-mcp-market`	Codex plugin, skill, marketplace metadata, and client wrapper scripts.

The goal of this repository is to replace the previous three-repository release chain with one source of truth. Docker images are built from the checked-in PoB vendor tree instead of cloning another repository during image build.

Local Validation

npm --prefix packages/pob-mcp ci
npm run validate
docker build -t pob-mcp-suite:local .
docker run --rm --entrypoint node -e POB_LUA_ENABLED=true -e POE_TRADE_ENABLED=false pob-mcp-suite:local /opt/pob-mcp/scripts/mcp-smoke.mjs node /opt/pob-mcp/build/index.js

Related MCP server: MCP-toolhouse

Release Shape

Root CI validates the MCP package and Codex plugin package.
Root Docker workflow builds the image from vendor/PathOfBuilding and packages/pob-mcp.
The Codex plugin continues to run ghcr.io/anitaguptaoffice/pob-mcp-suite:latest by default.
Existing standalone repositories can remain online during migration, but new changes should land here first.