Model Context Protocol (MCP) provides a standardized way for language-model applications to connect to external tools and information. For a coding agent working with Aspire, that connection helps it retrieve current information instead of guessing at APIs that may have changed. section 10.4 section 10.4.3
MCP and agentic tool calling are related but distinct. Tool calling is the agent’s decision to take an action, inspect its result, and decide what to do next. An agent might read files, run tests, or execute commands as part of that loop. MCP is a protocol for connecting the agent to capabilities it can use. section 10.4.3
An Aspire integration workflow
Start an existing .NET solution with `aspire init`, then run `aspire run`. The dashboard is initially blank because no projects have been added. Leave it running while setting up MCP and the coding assistant to work on the existing application. section 10.4













