Get the FREE Ultimate OpenClaw Setup Guide →

awesome-copilot-custom

MCP server from BrettOJ/awesome-copilot-custom-mcp-server

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio brettoj-awesome-copilot-custom-mcp-server dotnet run --project ./src/McpSamples.AwesomeCopilot.HybridApp \
  --env GITHUB__TOKEN="your_github_token_here"

How to use

This MCP server integrates GitHub Copilot customizations from the mbs-copilot-devcontext repository and exposes tooling to search and load Copilot instructions, as well as prompts to facilitateCopilot-related workflows. The server relies on a GitHub token to authenticate with the GitHub API and fetch repository data. Once the MCP server is running, you can access its tools and prompts through the host MCP environment (for example, via a VS Code MCP integration) using the available commands: search_instructions to find relevant custom instructions by keywords, load_instruction to retrieve a specific instruction from the repository, and get_search_prompt to obtain a suitable prompt for performing a Copilot instruction search.

How to install

Prerequisites:

  • .NET 9 SDK
  • Visual Studio Code (optional) with C# Dev Kit
  • Docker Desktop (for container runs)
  • Azure CLI and Azure Developer CLI (optional for deployment to Azure)
  • GitHub Personal Access Token (for access to the awesome-copilot repository)

Installation steps:

  1. Prepare your environment:
    • Ensure .NET 9 SDK is installed and available in your PATH.
    • Ensure Docker is installed if you plan to run in a container.
    • Create a GitHub token with access to the relevant repositories.
  2. Clone or obtain the MCP server repository and navigate to the project root.
  3. Build and run locally:
    • Run the MCP server using the provided project path: dotnet run --project ./src/McpSamples.AwesomeCopilot.HybridApp
    • Ensure you have GITHUB__TOKEN set in your environment or in a local .env file as described in the README.
  4. (Optional) Run in Docker:
    • Build the container image as demonstrated in the documentation, then run with the appropriate -e GITHUB__TOKEN environment variable and optional --http flag as needed.
  5. Verify access to the MCP server and its tools via your MCP host/client integration.

Tip: If you modify environment defaults (repository owner/name/branch), set them via a .env file or environment variables (GITHUB__TOKEN, GITHUB__REPOSITORYOWNER, GITHUB__REPOSITORYNAME, GITHUB__BRANCH) as described in the configuration section of the README.

Additional notes

Environment variable recommendations:

  • GITHUB__TOKEN: Required for authentication with the GitHub API.
  • Optional overrides: GITHUB__REPOSITORYOWNER, GITHUB__REPOSITORYNAME, GITHUB__BRANCH to customize the target repository and branch. Common issues:
  • If GITHUB__TOKEN is missing, the server startup may fail due to authentication errors.
  • When running in containers, remember to pass GITHUB__TOKEN as an environment variable; the token should not be hard-coded.
  • In production or Azure deployments, follow the deployment guidance in the README to set environment variables in the deployment environment before starting the MCP server.

Related MCP Servers

Sponsor this space

Reach thousands of developers