create_org_webhookLABSCO SUMMARY
Webhook administration is repetitive and clicky; this turns it into a sentence.
The organisation-level tools are what earn the server: one hook created there covers every repository, and listing them is how you find the stale endpoints nobody remembers adding. Updates are partial, so you can repoint a URL or narrow an event list without restating the rest of the configuration.
What it is
A server for GitHub webhook administration at both levels: hooks that apply to every repository in an organisation, and hooks on one repository.
What you get
- Organisation-wide webhooks created, listed with paging, modified and deleted (create_org_webhook, list_org_webhooks, update_org_webhook, delete_org_webhook)
- The same four operations on a single repository's hooks (create_repo_webhook, list_repo_webhooks, update_repo_webhook, delete_repo_webhook)
- Full control of the hook configuration — delivery URL, content type and shared secret — and the list of events it subscribes to
- A hook switched off without deleting it, by flipping its active flag
Requirements
A GitHub personal access token carrying the webhook administration scope for the level you are working at — organisation hooks and repository hooks need different ones. Node.js, with the token supplied as an environment setting.
Setup effort
Build from source
USE CASES
01
Auditing what is already wired up
List the organisation's hooks and the repository's, and see which delivery URLs are still live.
02
Adding one integration everywhere
Create a single organisation-level hook with the events you want, rather than repeating it per repository.
03
Repointing an endpoint that moved
Update just the delivery URL and leave the rest of the configuration alone.
04
Turning a noisy hook off without losing it
Set it inactive, then enable it again once the receiver is fixed.
05
Cleaning up after a decommissioned service
Find its hooks and delete them at both levels.
8 tools
Listed in project docs. Your client may show a different list.
list_org_webhooksupdate_org_webhookdelete_org_webhookcreate_repo_webhooklist_repo_webhooksupdate_repo_webhookdelete_repo_webhookBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- Node.js 18 or later
- GITHUB_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/ajaychinthapalli/github-webhooks-mcp-server
cd github-webhooks-mcp-server
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"github-webhooks": {
"command": "node",
"args": [
"<YOUR_PATH_TO_GITHUB_WEBHOOKS_MCP_SERVER>/dist/index.js"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}
