Runtime evidence for your agent, not guesswork from code.
When a service fails, the agent works from what the app is actually doing: which resource is unhealthy, what its logs say and where the trace breaks across services.
What it is
The MCP server built into the Aspire CLI. Aspire is Microsoft's toolchain for building and running distributed apps, describing services, containers and databases in code. This server shows an agent what your app is actually doing while it runs locally, so it does not have to guess from the source code.
What you get
- Every resource in the app with its state, health, endpoints and available commands
- Console logs, structured logs and distributed traces, filtered by resource or trace
- Resources started, stopped or restarted
- The right app chosen when several are running locally
- Aspire integration packages listed, with their docs
- Aspire documentation searched and read
- A setup check that diagnoses problems with your Aspire environment
Requirements
The Aspire CLI installed; the server starts with the command aspire agent mcp. An Aspire app running locally for live data. It is for local development, needs no account or key, and does not expose source code, environment variable values or secrets. You can hide sensitive resources and their logs from it in your app definition. Microsoft's first recommendation is its Aspire skills; this server gives the same data as tools.
Setup effort
One command — aspire agent mcp