poi-plugin-mcp

Poi plugin that starts a local HTTP/MCP bridge inside Poi so CLI/MCP agents can read current KanColle data.

Install

Install it from Poi's plugin manager as:

poi-plugin-mcp

Or install it into Poi's plugin directory with npm:

cd "$env:APPDATA\poi\plugins"
npm install poi-plugin-mcp

Then restart Poi and enable MCP Data Bridge if needed.

Development Install

When working from this repository, install from the repo root:

npm install
npm run install:poi

Then restart Poi and enable MCP Data Bridge if needed.

The installer creates:

%APPDATA%\poi\plugins\node_modules\poi-plugin-mcp -> <repo>\packages\poi-plugin-mcp

Settings

The Poi plugin settings panel supports:

• changing the HTTP port, saved in ~/.poi-mcp/settings.json
• manually starting and stopping the local bridge

The default port is 17777.

HTTP Endpoints

| Endpoint | Data | |---|---| | /health | Bridge status | | /basic | Admiral profile | | /fleets | Raw Poi fleet data | | /ships | Raw owned ship instance data | | /equipment | Raw owned equipment instance data | | /resources | Resource array | | /quests | Active quests and quest records | | /airbase | Land base air squadron data | | /names | Ship, equipment, and mission name maps | | /master | Master ship, equipment, ship type, equipment type, and mission data | | /event | Event ship tag definitions plus owned ships' current sally area | | /planner | Ship Info deck planner areas and ship assignments | | /all | Combined basic runtime data |

MCP Endpoint

The same local server also exposes a JSON-RPC MCP endpoint:

POST http://127.0.0.1:17777/mcp

It supports initialize, ping, resources/list, resources/read, tools/list, and tools/call. Resource URIs mirror the HTTP endpoints, including poi://ships, poi://equipment, poi://resources, poi://master, poi://event, and poi://planner.

Available tools:

• get_fleet_status
• search_ships
• search_equipment
• get_resources
• get_all

Verification

From the repo root:

npm run test:plugin