diff --git a/src/frontend/src/content/docs/dashboard/overview.mdx b/src/frontend/src/content/docs/dashboard/overview.mdx
index 8777c3707..8ade3c1b7 100644
--- a/src/frontend/src/content/docs/dashboard/overview.mdx
+++ b/src/frontend/src/content/docs/dashboard/overview.mdx
@@ -28,6 +28,12 @@ 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/).
 
+## AI coding agents
+
+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.
+
+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
 
 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/).