Schema | GitHub Webhooks MCP Server

GitHub Webhooks MCP Server

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)

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`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

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ajaychinthapalli/github-webhooks-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server