Github Webhook Mcp
Wire live GitHub push, PR, and issue events into Claude Code or Cursor through an MCP server instead of polling the API.
Overview
github-webhook-mcp is a Build-phase MCP server that streams GitHub webhook events into coding agents through a Cloudflare Worker relay.
What is this MCP server?
- Streams GitHub webhook payloads through a Cloudflare Worker into a stdio MCP server (npm github-webhook-mcp, npx)
- Configurable WEBHOOK_WORKER_URL for your deployed worker; optional WEBHOOK_CHANNEL to enable or disable SSE channel noti
- Version 0.8.2 package with stdio transport—no custom MCP host code required on the agent machine
- Keeps GitHub event context inside the agent session so you can react to pushes and PRs without leaving the editor
- Fits indie workflows that already use Cloudflare at the edge and want a thin webhook relay instead of a full self-hosted
- npm package github-webhook-mcp at version 0.8.2
- 2 documented environment variables: WEBHOOK_WORKER_URL and WEBHOOK_CHANNEL
- Single stdio transport entry via npx per server.schema.json packages block
What problem does it solve?
Coding agents lack timely awareness of what changed on GitHub unless you poll APIs or copy event details by hand.
Who is it for?
Solo builders who deploy or reuse the project's Cloudflare Worker, use MCP in Claude Code or Cursor, and want lightweight real-time repo signals without running a dedicated webhook server at home.
Skip if: Teams that need a managed GitHub App with rich REST tooling, enterprise audit pipelines, or production incident monitoring without touching Workers or webhook secrets.
What do I get? / Deliverables
After you configure the worker URL and MCP entry, webhook-driven GitHub activity becomes available inside your agent session for faster, context-aware responses.
- Stdio MCP server connected to GitHub webhook events via the worker bridge
- Optional SSE channel notifications when WEBHOOK_CHANNEL is enabled
- Agent-accessible stream of repo activity for integration and automation prompts
Recommended MCP Servers
Journey fit
Connecting GitHub webhooks to your agent stack is integration work you do while building and maintaining repos with AI-assisted workflows, before you rely on those hooks for ship or operate automation. The integrations shelf is where third-party services—here GitHub plus a Cloudflare Worker bridge—are registered as MCP tools your coding agent can consume in real time.
How it compares
MCP GitHub event streaming through an edge worker, not a general GitHub API skill or a hosted marketplace catalog.
Common Questions / FAQ
Who is github-webhook-mcp for?
It is for indie and solo developers using MCP-enabled coding agents who want GitHub webhook events in the same session where they write and review code.
When should I use github-webhook-mcp?
Use it when you are wiring GitHub into agent workflows during build or early operate setups and need near-real-time events instead of manual status checks.
How do I add github-webhook-mcp to my agent?
Deploy or use the Cloudflare Worker, set WEBHOOK_WORKER_URL (and WEBHOOK_CHANNEL if needed), point GitHub webhooks at the worker, then add a stdio MCP server entry that runs npx github-webhook-mcp in your Claude or Cursor MCP configuration.