Is Docker required to use the awesome-copilot MCP server?
I want to try the awesome-copilot MCP server on a low-resource machine, but Docker is too heavy a dependency. A closed issue on github/awesome-copilot asks for Docker to be made optional. Is Docker actually required, or is there a supported way to install and use it without Docker? No error message is involved; this is about setup options for weaker hardware.
Originally asked on GitHub: https://github.com/github/awesome-copilot/issues/358
4 answers
Docker is not a mandatory dependency for awesome-copilot; it is only described as the simplest install path. The issue was closed as completed after a contributor explained the Docker-free options.
The contributor pointed to two things:
- You can build and run the MCP server yourself using the instructions in the microsoft/mcp-dotnet-samples repo under
awesome-copilot(https://github.com/microsoft/mcp-dotnet-samples/tree/main/awesome-copilot (opens external site)). The awesome-copilot repo also contains prompts that search the repo and suggest which items to install. - A new collection was added at https://github.com/github/awesome-copilot/blob/main/collections/awesome-copilot.md (opens external site) to make installable items easier to discover.
Note that the thread only points to these options; nobody in the thread reports having run the build-it-yourself path, so treat it as an unverified alternative rather than a confirmed working setup.
A commenter also shared the Prompt Registry VS Code extension (v0.0.3, by AmadeusITGroup) as a Docker-free way to install copilot resources: trigger
Prompt Registry: Scaffold Awesome-Copilot Project(Ctrl+Shift+P), customize the generated folder, push it to GitHub (public or private), then add the repo as a source in the extension. The commenter added that simpler installation flows are still being explored, so this is an in-progress alternative.General advice: if you try building from source and hit an error, check that your .NET SDK version matches what the MCP server repo specifies.
Did this work for you?- You can build and run the MCP server yourself using the instructions in the microsoft/mcp-dotnet-samples repo under
What a GitHub user tried on GitHub (Outcome unclear)
Reporter requested that Docker become optional because it is resource-intensive on weaker machines. This is a feature request, not an installation attempt.
Source: https://github.com/github/awesome-copilot/issues/358 (opens external site)
Did this work for you?What @aaronpowell tried on GitHub (Outcome unclear)
Contributor stated Docker is not required and pointed to the microsoft/mcp-dotnet-samples instructions for building/running the MCP server yourself, plus a new collection for discovering items. The thread does not report anyone actually testing these instructions.
Source: https://github.com/github/awesome-copilot/issues/358#issuecomment-3459219368 (opens external site)
Did this work for you?What @wherka-ama tried on GitHub (Outcome unclear)
Commenter suggested the Prompt Registry VS Code extension as a Docker-free way to scaffold and install collections, noting the project is still exploring simpler installation flows. No user in the thread confirms this path works.
Source: https://github.com/github/awesome-copilot/issues/358#issuecomment-3514092344 (opens external site)
Did this work for you?
Related questions
- Which MCP servers does an awesome-copilot prompt or chat mode need?
- How do I use awesome-copilot without an MCP server?
- VS Code prompt files: is `mode` deprecated, should I use `agent`?
- Why is the awesome-copilot plugin missing from the Copilot CLI marketplace?
- az devops invoke fails with 'could not convert string to float' when using --api-version