Introspection is a development concern, so it belongs to the build rather than to the application.
Declaring it in the app would put a development tool in the application's own module graph — and
make a production build depend on a package the application does not need — for a feature nobody
uses in production. The build already knows when a developer is working, which is exactly when this
is wanted, so the build is where it is decided.
What it does, in one sentence: on a development build it injects a hook that makes the running
application publish its resolved configuration, so stone mcp describes that application
instead of the console boot it can reach by itself.
Nothing is injected into a production build, and nothing has to be imported by the app.
The MCP dev CLI plugin.
Introspection is a development concern, so it belongs to the build rather than to the application. Declaring it in the app would put a development tool in the application's own module graph — and make a production build depend on a package the application does not need — for a feature nobody uses in production. The build already knows when a developer is working, which is exactly when this is wanted, so the build is where it is decided.
What it does, in one sentence: on a development build it injects a hook that makes the running application publish its resolved configuration, so
stone mcpdescribes that application instead of the console boot it can reach by itself.Nothing is injected into a production build, and nothing has to be imported by the app.