Skill detail
aspire
Aspire skill covering the Aspire CLI, AppHost orchestration, service discovery, integrations, MCP server, VS Code extension, Dev Containers, GitHub Codespaces, templates, dashboard, and deployment. Use when the user asks to create, run, debug, configure, deploy, or troubleshoot an Aspire…
Why we recommend it: Aspire orchestration with a VS Code extension mention, but primarily distributed-app tooling.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- name: aspire description: 'Aspire skill covering the Aspire CLI, AppHost orchestration, service discovery, integrations, MCP server, VS Code extension, Dev Containers, GitHub Codespaces, templates, dashboard, and deployment. Use when the user asks to create, run, debug, configure, deploy, or troubleshoot an Aspire distributed application.' --- # Aspire — Polyglot Distributed-App Orchestration Aspire is a **code-first, polyglot toolchain** for building observable, production-ready distributed applications. It orchestrates containers, executables, and cloud resources from a single AppHost project — regardless of whether the workloads are C#, Python, JavaScript/TypeScript, Go, Java, Rust, Bun, Deno, or PowerShell. > **Mental model:** The AppHost is a *conductor* — it doesn't play the instruments, it tells every service when to start, how to find each other, and watches for problems. Detailed reference material lives in the `references/` folder — load on demand. --- ## References | Reference | When to load | |---|---| | [CLI Reference](references/cli-reference.md) | Command flags, options, or detailed usage | | [MCP Server](references/mcp-server.md) | Setting up MCP for AI assistants, available tools | | [Integrations Catalog](references/integrations-catalog.md) | Discovering integrations via MCP tools, wiring patterns | | [Polyglot APIs](references/polyglot-apis.md) | Method signatures, chaining options, language-specific patterns | | [Architecture](references/architecture.md) | DCP internals, resource model, service discovery, networking, telemetry | | [Dashboard](references/dashboard.md) | Dashboard features, standalone mode, GenAI Visualizer | | [Deployment](references/deployment.md) | Docker, Kubernetes, Azure Container Apps, App Service | | [Testing](references/testing.md) | Integration tests against the AppHost | | [Troubleshooting](references/troubleshooting.md) | Diagnostic codes, common errors, and fixes | --- ## 1. Researching Aspire Documentation The Aspire team ships an **MCP server** that provides documentation tools directly inside your AI assistant. See [MCP Server](references/mcp-server.md) for setup details. ### Aspire CLI 13.2+ (recommended — has built-in docs search) If running Aspire CLI **13.2 or later** (`aspire --version`), the MCP server includes docs search tools: | Tool | Description | |---|---| | `list_docs` | Lists all available documentation from aspire.dev | | `search_docs` | Performs weighted lexical search across indexed documentation | | `get_doc` | Retrieves a specific document by its slug | These tools were added in [PR #14028](https://github.com/dotnet/aspire/pull/14028). To update: `aspire update --self --channel daily`. For more on this approach, see David Pine's post: https://davidpine.dev/posts/aspire-docs-mcp-tools/ ### Aspire CLI 13.1 (integration tools only) On 13.1, the MCP server provides integration lookup but **not** docs search: | Tool | Description | |---|---| | `list_integrations` | Lists available Aspire hosting integrations | | `get_integration_docs` | Gets documentation for a specific integration package | For general docs queries on 13.1, use **Context7** as your primary source (see below). ### Fallback: Context7 Use **Context7** (`mcp_context7`) when the Aspire MCP docs tools are unavailable (13.1) or the MCP server isn't running: **Step 1 — Resolve the library ID** (one-time per session): Call `mcp_context7_resolve-library-id` with `libraryName: ".NET Aspire"`. | Rank | Library ID | Use when | |---|---|---| | 1 | `/microsoft/aspire.dev` | Primary source. Guides, integrations, CLI reference, deployment. | | 2 | `/dotnet/aspire` | API internals, source-level implementation details. | | 3 | `/communitytoolkit/aspire` | Non-Microsoft polyglot integrations (Go, Java, Node.js, Ollama). | **Step 2 — Query docs:** ``` libraryId: "/microsoft/aspire.dev", query: "Python integration AddPythonApp service discovery" libraryId: "/communitytoolkit/aspire", queRead the full source on GitHub (opens external page)