This is what makes stone mcp describe the application a developer is actually running. The MCP
server is a console command: booting the app itself gives it the console platform, so its
adapters, its response type and every platform-conditional contribution belong to a different
application than the one under stone dev. The running app knows the truth, so the running app
says it.
A file rather than an endpoint, deliberately. The Blueprint is the Setup dimension: assembled once
before the first event and then read, so publishing it once at boot is not a snapshot of something
moving — it is the value. A file also needs no port to discover, no dev-only route in someone's
application, no token to protect, and it works for a CLI or an edge context that has no HTTP
surface at all. What genuinely moves at run time (a live configuration, metrics) is a different
question, and belongs to a different tool.
Publish an application's resolved configuration.
This is what makes
stone mcpdescribe the application a developer is actually running. The MCP server is a console command: booting the app itself gives it the console platform, so its adapters, its response type and every platform-conditional contribution belong to a different application than the one understone dev. The running app knows the truth, so the running app says it.A file rather than an endpoint, deliberately. The Blueprint is the Setup dimension: assembled once before the first event and then read, so publishing it once at boot is not a snapshot of something moving — it is the value. A file also needs no port to discover, no dev-only route in someone's application, no token to protect, and it works for a CLI or an edge context that has no HTTP surface at all. What genuinely moves at run time (a
liveconfiguration, metrics) is a different question, and belongs to a different tool.