MCP server on the official SDK, over stdio or HTTP
scripts/mcp.js registers the same tools on @modelcontextprotocol/server (2.4.0, with @modelcontextprotocol/node 2.1.2 for node:http; dev dependencies, pinned) instead of its own JSON-RPC loop. stdio works as before; --http [HOST:]PORT serves Streamable HTTP at /mcp, on loopback unless told otherwise. Over HTTP every request's Host must be an address of this machine (or --allow-host), an Origin other than localhost is refused, and a bearer token (SOT_MCP_TOKEN or --token-file) is optional; bound beyond loopback without one, the server warns. load_save and export_save take JSON only there, or files under --save-dir and nowhere else. Calls from every client run one at a time, in order.
This commit is contained in:
parent
5b76685e5c
commit
2526dd458d
11 changed files with 467 additions and 63 deletions
|
|
@ -56,7 +56,7 @@ npm run dev # development server: assembles src/ on every request, reloads on
|
|||
npm test # headless tests: boot, geography, a year of play, every incident, every panel
|
||||
npm run build # writes the site for GitHub Pages to _site/, with version and date stamped in
|
||||
npm run i18n:check # lists text missing from (or stale in) the translations
|
||||
npm run mcp # the game as an MCP server, so an AI client can play and debug it (docs/MCP.md)
|
||||
npm run mcp # the game as an MCP server, so an AI client can play and debug it (docs/MCP.md; --http for HTTP)
|
||||
```
|
||||
|
||||
## Community
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue