Armin Ronacher 7dc38ff0e9 feat(p2): MCP servers on the host, on environments and from projects ... A manager on the p2 server owns every MCP connection and process. Session workers hold one view each and lease the locations their conversations work at; the manager runs the owner's mcp.json servers there (stdio per session and location, or shared; HTTP shared by default) and offers their tools as deferred Durable tools found through tool_search. Stdio servers on an environment start through its pi-env daemon, one connection per environment shared by its instances, through cmd.exe on Windows. A project's .pi/mcp.json, read by the worker at each location, may add stdio servers that run there and switch the owner's servers on or off; the manager refuses everything else. A lease gets servers only on environments its session works on.		2026-11-03 16:48:38 +01:00
..
p2	feat(p2): MCP servers on the host, on environments and from projects	2026-11-03 16:48:38 +01:00