GitHub Webhooks MCP Server
Allows managing GitHub webhooks at organization and repository levels, including creating, listing, updating, and deleting webhooks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GitHub Webhooks MCP Server create repo webhook for push events"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GitHub Webhooks MCP Server
A Model Context Protocol (MCP) server for managing GitHub webhooks at both organization and repository levels.
Features
Organization-level Webhooks
create_org_webhook - Create webhooks that apply to all repositories in an organization
list_org_webhooks - List all organization-level webhooks
update_org_webhook - Modify existing organization webhooks
delete_org_webhook - Remove organization webhooks
Repository-level Webhooks
create_repo_webhook - Create webhooks for a specific repository
list_repo_webhooks - List all webhooks for a repository
update_repo_webhook - Modify existing repository webhooks
delete_repo_webhook - Remove repository webhooks
Related MCP server: GitHub Tools MCP Server
Installation
npm install
npm run buildConfiguration
The server requires a GitHub personal access token with appropriate permissions:
For organization webhooks:
admin:org_hookscopeFor repository webhooks:
admin:repo_hookscope
Set the token as an environment variable:
export GITHUB_TOKEN=your_github_token_hereUsage
Running the Server
node dist/index.jsMCP Client Configuration
Add to your MCP client configuration (e.g., Claude Desktop):
{
"mcpServers": {
"github-webhooks": {
"command": "node",
"args": ["/path/to/github-webhooks-mcp-server/dist/index.js"],
"env": {
"GITHUB_TOKEN": "your_github_token_here"
}
}
}
}Tool Examples
Create Organization Webhook
{
"org": "my-org",
"config": {
"url": "https://example.com/webhook",
"content_type": "json",
"secret": "my-secret"
},
"events": ["push", "pull_request"],
"active": true
}List Organization Webhooks
{
"org": "my-org",
"per_page": 30,
"page": 1
}Update Organization Webhook
{
"org": "my-org",
"hook_id": 12345,
"config": {
"url": "https://example.com/new-webhook"
},
"active": false
}Delete Organization Webhook
{
"org": "my-org",
"hook_id": 12345
}Create Repository Webhook
{
"owner": "username",
"repo": "repository-name",
"config": {
"url": "https://example.com/webhook",
"content_type": "json"
},
"events": ["push", "issues"],
"active": true
}List Repository Webhooks
{
"owner": "username",
"repo": "repository-name"
}Update Repository Webhook
{
"owner": "username",
"repo": "repository-name",
"hook_id": 12345,
"events": ["push", "pull_request", "issues"]
}Delete Repository Webhook
{
"owner": "username",
"repo": "repository-name",
"hook_id": 12345
}Webhook Events
Common webhook events include:
push- Git push to a repositorypull_request- Pull request activityissues- Issue activityissue_comment- Issue comment activityrelease- Release activitycreate- Branch or tag createddelete- Branch or tag deletedfork- Repository forkedstar- Repository starredwatch- Repository watched
For a complete list of events, see GitHub Webhook Events Documentation.
Development
Build
npm run buildProject Structure
github-webhooks-mcp-server/
├── src/
│ └── index.ts # Main server implementation
├── dist/ # Compiled JavaScript (generated)
├── package.json
├── tsconfig.json
└── README.mdRequirements
Node.js 18 or higher
GitHub personal access token with appropriate webhook permissions
License
MIT
Available Tools
8 toolscreate_org_webhookA
Create a webhook for an organization that applies to all repositories in the organization
Inputs: org (required), config (required), name, active, +1 more.
create_repo_webhookB
Create a webhook for a specific repository
Inputs: repo (required), owner (required), config (required), name, +2 more.
delete_org_webhookA
Delete an organization webhook
Inputs: org (required), hook_id (required).
delete_repo_webhookC
Delete a repository webhook
Inputs: repo (required), owner (required), hook_id (required).
list_org_webhooksB
List all webhooks for an organization
Inputs: org (required), page, per_page.
list_repo_webhooksA
List all webhooks for a repository
Inputs: repo (required), owner (required), page, per_page.
update_org_webhookB
Update an existing organization webhook
Inputs: org (required), hook_id (required), active, config, +1 more.
update_repo_webhookB
Update an existing repository webhook
Inputs: repo (required), owner (required), hook_id (required), active, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct resource type (org vs repo) and action (list/create/update/delete), with no overlap. The org and repo scopes are clearly separated in both names and descriptions.
All tool names follow the consistent pattern verb_scope_webhook (e.g., create_org_webhook, delete_repo_webhook). No mixed conventions or vague verbs.
8 tools is well-scoped for managing webhooks across two levels (org and repo). Each tool serves a clear purpose, and the count is within the ideal range.
The tool set provides full CRUD coverage for both organization and repository webhooks. There are no missing operations that would cause dead ends—list returns IDs needed for update/delete, so workflows are complete.
Maintenance
Related MCP Connectors
Create, deploy, and operate MCP servers directly from your GitHub repositories.
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
A MCP server built for developers enabling Git based project management with project and personal…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLM agents to manage GitHub repositories, issues, pull requests, branches, files, and releases through a standardized interface.8Apache 2.0
- FlicenseNot gradedqualityNot gradedmaintenanceModel Context Protocol server that enables interaction with GitHub repositories, issues, pull requests, and search functionality through natural language.1-
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that enables remote connections with GitHub authentication, allowing users to build applications that leverage MCP tools with secure OAuth-based access control.GPL 3.0
- AlicenseBqualityDmaintenanceMCP (Model Context Protocol) server for GitHub API integration. This server provides comprehensive tools for interacting with GitHub repositories, issues, pull requests, branches, and code search through a unified interface.157 npmMIT