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
|
|
@ -31,6 +31,10 @@ one, redesign the feature.
|
|||
- **Limits:** about 1 GB for the whole site, 100 MB per file.
|
||||
- **Paths:** the site lives at the domain root (`site/CNAME`), so `/` paths are fine; unknown paths get
|
||||
`404.html`.
|
||||
- **Local tools are not hosting.** `npm run dev` and the MCP server (`npm run mcp`, also over `--http`)
|
||||
run on a developer's own machine against a checkout; nothing they serve is deployed, and the game
|
||||
never depends on them. Their code stays out of `_site/` (`src/agent/` is development-only, see
|
||||
`docs/adr/0004-dev-only-code.md`).
|
||||
|
||||
## How it deploys
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue