MCP server wrapper for GitHub MCP — interact with GitHub repositories, issues, pull requests, and code search via the GitHub Copilot API. See github/github-mcp-server for full documentation.
GitHub MCP exposes the GitHub API as MCP tools, letting AI assistants read and create issues, comment on pull requests, search code, browse repository trees, and perform other GitHub operations on your behalf. In production the Hackerdogs integration connects to the hosted endpoint at https://api.githubcopilot.com/mcp/ using your GitHub token. This Docker image is a local compliance stub that satisfies MCP server shape requirements for CI and offline use.
GitHub token required for production use — configure a Personal Access Token or GitHub App token with the appropriate repository scopes.
| Tool | Description |
|---|---|
remote_endpoint_info | Return the official remote MCP URL and notes for this integration. |
Here are example prompts you can use with Claude (or any MCP client) when this tool is connected:
legacy_auth()."docker-compose up -d
docker run -i --rm hackerdogs/github-mcp:latest
docker run -d -p 8521:8521 \
-e MCP_TRANSPORT=streamable-http \
-e MCP_PORT=8521 \
hackerdogs/github-mcp:latest
Add to your Claude Desktop or Cursor MCP config:
{
"mcpServers": {
"github-mcp": {
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT", "hackerdogs/github-mcp:latest"],
"env": {
"MCP_TRANSPORT": "stdio"
}
}
}
}
First, start the server using Docker Compose or docker run with HTTP mode (see Deploy above), then point your MCP client at the running server:
{
"mcpServers": {
"github-mcp": {
"url": "http://localhost:8521/mcp"
}
}
}
When to use HTTP mode: HTTP mode is ideal for shared/remote deployments, multi-user setups, and Hackerdogs scheduled prompts. The server runs as a long-lived process and accepts connections from multiple MCP clients concurrently.
| Variable | Default | Description |
|---|---|---|
MCP_TRANSPORT | stdio | Transport mode: stdio or streamable-http |
MCP_PORT | 8521 | HTTP port (only used with streamable-http) |
The fastest way to get started is through Hackerdogs:
Give it a couple of minutes to go live. Then start querying by asking Hackerdogs to use the tool explicitly (e.g. "Use naabu to scan example.com"). If you don't specify, Hackerdogs will automatically choose the best tool for the job — it may choose this one on its own.
Want to contribute or chat with the team? Join our Discord.
docker build -t hackerdogs/github-mcp:latest .
./test.sh
1. Start the server in HTTP mode:
docker run -d --rm --name github-mcp-test -p 8521:8521 \
-e MCP_TRANSPORT=streamable-http \
hackerdogs/github-mcp:latest
2. Initialize the MCP session:
SESSION_ID=$(curl -s -D - -X POST http://localhost:8521/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}}}' \
2>&1 | grep -i mcp-session-id | awk '{print $2}' | tr -d '\r\n')
curl -s -X POST http://localhost:8521/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","method":"notifications/initialized"}'
3. Call a tool:
curl -s -X POST http://localhost:8521/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"run_github","arguments":{"arguments":"--help"}}}'
4. Clean up:
docker stop github-mcp-test
You can run the Github CLI in the same container by overriding the entrypoint without starting the MCP server.
Show help:
docker run -i --rm --entrypoint github hackerdogs/github-mcp:latest --help
Content type
Image
Digest
sha256:50e4e6446…
Size
71.5 MB
Last updated
4 months ago
docker pull hackerdogs/github-mcp