Awesome Copilot

You can run the Awesome Copilot MCP Server to access awesome-copilot agents and collection resources through a Model Context Protocol interface. This server can operate locally via stdio or be exposed over HTTP for remote access and testing with OpenAPI tooling.

How to use

You interact with the MCP server from an MCP client. Choose either a local, inline stdio configuration or an HTTP server for remote access.

How to install

Prerequisites you need before starting are: Node.js and npm (or a compatible Node.js environment). Ensure you have internet access to fetch the MCP package.

# Install prerequisites if needed (check your OS package manager)
# Node 18+ is commonly recommended
# Verify npm version
node -v
npm -v

To run the MCP server locally using the standard MCP command, use the following command. This starts the server in stdio mode and will load the latest MCP version each time you run it.

npx -y awesome-copilot-mcp start

If you prefer to expose the server over HTTP for remote access or API testing, start the HTTP server with these options. This example binds to port 8080 on all interfaces.

npx -y awesome-copilot-mcp start-http --port 8080 --host 0.0.0.0

Optionally, configure a client to connect to the server. You can specify the MCP server under the mcpServers configuration in your client setup, using the same commands shown above.

Configuration and usage notes

Environment variables can influence how the MCP server behaves. The following variables are supported in this setup.

ACP_METADATA_URL: Optional. URL to a hosted metadata.json. Overrides the GitHub raw fetch when provided.
ACP_REPOS_JSON: Custom repository configuration JSON.

The server’s runtime metadata is kept in memory for the current session. It loads embedded metadata on startup and refreshes from GitHub as needed without writing to disk.

Additional sections

Tools and endpoints exposed by the MCP server include health checks, metadata streams, search, and API documentation. These capabilities enable you to verify server health, discover available agents and resources, search for content, and inspect the OpenAPI description for integration tests.

Security and environment considerations

When exposing the MCP server over HTTP, ensure your network and firewall configurations align with your security requirements. Use the host binding option to restrict access as needed and consider HTTPS in production environments.

Available tools

health

Endpoint to check the server health and readiness.

metadata

Endpoint to retrieve the metadata index and stream updates via server-sent events.

search

Endpoint to search available agents, prompts, and resources using a query parameter.

openapi

Endpoint to access the OpenAPI specification for integration testing and tooling.