The MCP server is a console command, so the blueprint it holds is the one a console boot resolves:
its adapter, its response type and every platform-conditional contribution belong to a different
application than the one running under stone dev. When the running application has published its
own configuration, that is the better answer and it is used; otherwise the console boot still
answers for everything platform-independent — routes, providers, the kernel handler — and says which
of its answers not to trust, rather than pretending to be the running app.
Parameters
blueprint: IBlueprint
The blueprint of the process the MCP server runs in.
What the tools are describing, and how they know.
The MCP server is a console command, so the blueprint it holds is the one a console boot resolves: its adapter, its response type and every platform-conditional contribution belong to a different application than the one running under
stone dev. When the running application has published its own configuration, that is the better answer and it is used; otherwise the console boot still answers for everything platform-independent — routes, providers, the kernel handler — and says which of its answers not to trust, rather than pretending to be the running app.