From 9bed93d58e51c682db80809619f55eed7708d926 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 2 Jun 2026 09:35:59 +0000 Subject: [PATCH 1/3] Initial plan From 0a90efa6fbda9253780f8dc73de212299b6b6e66 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 2 Jun 2026 10:26:14 +0000 Subject: [PATCH 2/3] Update dashboard overview MCP and agent guidance Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com> --- src/frontend/src/content/docs/dashboard/overview.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/src/frontend/src/content/docs/dashboard/overview.mdx b/src/frontend/src/content/docs/dashboard/overview.mdx index 8777c3707..7a5ac89d9 100644 --- a/src/frontend/src/content/docs/dashboard/overview.mdx +++ b/src/frontend/src/content/docs/dashboard/overview.mdx @@ -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/). From f2c0c9387f3bfce8afb8c5ba97fbda0af0a66fb4 Mon Sep 17 00:00:00 2001 From: David Pine <7679720+IEvangelist@users.noreply.github.com> Date: Fri, 7 Aug 2026 11:40:01 -0500 Subject: [PATCH 3/3] Address dashboard AI agent review feedback Clarify MCP startup, distinguish AppHost and dashboard-only tool access, and remove the screenshot TODO. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- src/frontend/src/content/docs/dashboard/overview.mdx | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/src/frontend/src/content/docs/dashboard/overview.mdx b/src/frontend/src/content/docs/dashboard/overview.mdx index 7a5ac89d9..8ade3c1b7 100644 --- a/src/frontend/src/content/docs/dashboard/overview.mdx +++ b/src/frontend/src/content/docs/dashboard/overview.mdx @@ -28,15 +28,11 @@ 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 +## AI coding agents -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. +Run [`aspire agent mcp`](/reference/cli/commands/aspire-agent-mcp/) to start the MCP server and connect AI coding agents to dashboard data. With an AppHost connection, agents can inspect resource status and console logs, read structured logs and traces, and run resource commands. -{/* 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/). +When you connect directly to a standalone dashboard with `--dashboard-url`, only `list_structured_logs`, `list_traces`, and `list_trace_structured_logs` are available. The dashboard telemetry API must be enabled with `ApiKey` or `Unsecured` authentication; pass `--api-key` when API key authentication is enabled. For setup and examples, see [AI coding agents and the Aspire Dashboard](/dashboard/ai-coding-agents/). ## Standalone mode