GitHub Webhooks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token with appropriate permissions (admin:org_hook for org webhooks, admin:repo_hook for repo webhooks) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_org_webhookA | Create a webhook for an organization that applies to all repositories in the organization |
| list_org_webhooksB | List all webhooks for an organization |
| update_org_webhookB | Update an existing organization webhook |
| delete_org_webhookA | Delete an organization webhook |
| create_repo_webhookB | Create a webhook for a specific repository |
| list_repo_webhooksA | List all webhooks for a repository |
| update_repo_webhookB | Update an existing repository webhook |
| delete_repo_webhookC | Delete a repository webhook |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.