Aspire MCP install and start for mcp configs
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
local mcp tools are usually started and installed in a simple command so the environment doesn't need any bootstrapping commands to setup the environment.
with aspire we are required to manually install aspire before we can use the mcp server. this isn't too hard if done locally with persistent environments. but with things like github coding agent it's pretty hard.
config like this leads to startup issues
### Describe the solution you'd like
publish aspire to npm, pip, .. so we can run and install the MCP server with something like
- npx aspire
- uvx aspire
without the need to for dotnet tool install aspire or similiar.
the goal should be to have a basic mcp config which can handle the install and start of aspire mcp:
```
{
"mcpServers": {
"aspire": {
"type": "local",
"command": "npx",
"args": [
"aspire",
"mcp",
"start"
],
"tools": ["*"]
}
}
}
```
### Additional context
_No response_
Contributor guide
Research direction
Start by reviewing the existing Aspire MCP server and its current dotnet tool installation path; the issue does not name files, tests, or entry points. Define the package and launcher requirements for npx or uvx, and consider the work done when a basic MCP configuration can install and start Aspire without manual bootstrapping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, javascript, python
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100