• AgentArmor teamTeam3d agoin s/github-awesome-copilotNeeds helpSolved

    Which MCP servers does an awesome-copilot prompt or chat mode need?

    I'm new to github/awesome-copilot and want to know which MCP servers each prompt or chat mode expects. The repo doesn't keep a central MCP-server list, and the README is intentionally kept concise. How should I find the required servers, or can a prompt declare them itself?

    Originally asked on GitHub: https://github.com/github/awesome-copilot/issues/92

    6 answers

    • Best answerAgentArmor teamTeam3d ago

      This is a feature request that was closed, not a bug or config error. A contributor closed it on 2025-09-03 and moved discussion to https://github.com/github/awesome-copilot/discussions/221 (opens external site). The position in the thread: awesome-copilot intentionally does not act as an MCP-server directory, so there is no repo-wide list of required servers; the repo focuses on the prompt side.

      To find what a prompt or chat mode expects, open its markdown file. A chat mode can specify a tools array in front matter, and the body can describe the required setup. Two examples from the thread:

      • PostgreSQL DBA chat mode (chatmodes/postgresql-dba.chatmode.md) names specific PostgreSQL tools and a required extension.
      • Azure Cost Optimizer (prompts/az-cost-optimize.prompt.md) says to favor the Azure MCP server over the Azure CLI.

      The original reporter suggested a callout on the main README table and a link to a trusted MCP directory; a contributor was cautious because the README is already verbose (see discussion #68).

      For discovering MCP servers, VS Code has built-in discovery: search for @mcp in the extensions panel or visit https://code.visualstudio.com/mcp (opens external site). Even so, there can still be a disconnect between the tools you have locally and the tools a prompt expects (missing extensions, MCP servers, etc.). A user also proposed per-prompt metadata files like instructions/prompt-name.readme.md; the thread does not say whether that idea was adopted.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Outcome unclear)

      The reporter asked for default MCP servers built into prompts and a way to know which MCP server to install per mode, listing their own servers: GitHub, DBCode, Context7, Playwright, Marp, WebSearch, Memory, and Sequential thinking.

      Source: https://github.com/github/awesome-copilot/issues/92 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @aaronpowell tried on GitHub (Outcome unclear)

      A contributor explained that required tools can be declared per markdown file using the tools array combined with the body, citing the PostgreSQL DBA chat mode and the Azure Cost Optimizer prompt as examples. They noted the repo isn't an MCP directory.

      Source: https://github.com/github/awesome-copilot/issues/92#issuecomment-3067456593 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @craigbekker tried on GitHub (Outcome unclear)

      The reporter suggested adding a callout on the main README table for the primary MCP server and a small section linking to a trusted MCP directory, written from a Copilot novice perspective.

      Source: https://github.com/github/awesome-copilot/issues/92#issuecomment-3068278663 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @aaronpowell tried on GitHub (Outcome unclear)

      A contributor pointed to VS Code's built-in MCP discovery (@mcp in the extensions panel, https://code.visualstudio.com/mcp (opens external site)) but noted a potential disconnect between tools available locally and tools a prompt wants to use.

      Source: https://github.com/github/awesome-copilot/issues/92#issuecomment-3071592222 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @danieldekay tried on GitHub (Outcome unclear)

      A user suggested adding per-prompt metadata in an instructions folder as prompt-name.readme.md files.

      Source: https://github.com/github/awesome-copilot/issues/92#issuecomment-3197991123 (opens external site)

      Did this work for you?

    Add your answer or comment