Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions src/frontend/src/content/docs/dashboard/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,16 @@ The dashboard is integrated into the [Aspire _*.AppHost_](/get-started/app-host/

For more information about using the dashboard during Aspire development, see [Explore dashboard features](/dashboard/explore/).

## MCP server

The Aspire dashboard data can be exposed to external AI coding agents through the [Aspire MCP server](/get-started/aspire-mcp-server/). This gives agents access to resource status, structured logs, traces, and console output so they can investigate issues with the same telemetry data you see in the dashboard.

{/* TODO(screenshot): Before this docs update is shipped, add a screenshot that shows an external agent (for example, GitHub Copilot CLI) calling Aspire/MCP to fetch dashboard data and displaying reasoning/results. Do not use an in-dashboard Copilot chat UI screenshot. */}

### Using agents with the dashboard

Use AI coding agents with the dashboard by connecting your agent to Aspire CLI and MCP tools, then letting it query dashboard telemetry as part of debugging workflows. For setup and end-to-end examples, see [AI coding agents and the Aspire Dashboard](/dashboard/ai-coding-agents/).

## Standalone mode

The Aspire dashboard can run standalone, without the rest of Aspire. The standalone dashboard provides a great UI for viewing telemetry and can be used by any application that sends OpenTelemetry data. You can start it with the Aspire CLI or run it from the standalone container image. For more information, see the [Standalone Aspire dashboard](/dashboard/standalone/).
Expand Down