The GitHub MCP Server is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) server that provides seamless integration
Most monitoring and observability work still happens through a UI a human drives. Github Asifdotpy MCP server moves it into the conversation instead. The GitHub MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with GitHub APIs.
The server publishes 14 tools. What each one is for:
cancel_workflow_run — Cancel workflow runowner — Repository owner (string, required)repo — Repository name (string, required)run_id — The unique identifier of the workflow run (number, required)delete_workflow_run_logs — Delete workflow logsdownload_workflow_run_artifact — Download workflow artifactartifact_id — The unique identifier of the artifact (number, required)get_job_logs — Get job logsfailed_only — When true, gets logs for all failed jobs in run_id (boolean, optional)job_id — The unique identifier of the workflow job (required for single job logs) (number, optional)return_content — Returns actual log content instead of URLs (boolean, optional)get_workflow_run — Get workflow runBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: GITHUB_PERSONAL_ACCESS_TOKEN, GITHUB_HOST, TOOL_ADD_ISSUE_COMMENT_DESCRIPTION, TOOL_CREATE_BRANCH_DESCRIPTION, YOUR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Github Asifdotpy's toolset — cancel_workflow_run, owner, repo and 11 more — is a fair guide to whether it matches your workflow. It is maintained by asifdotpy; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| cancel_workflow_run | Cancel workflow run |
| owner | Repository owner (string, required) |
| repo | Repository name (string, required) |
| run_id | The unique identifier of the workflow run (number, required) |
| delete_workflow_run_logs | Delete workflow logs |
| download_workflow_run_artifact | Download workflow artifact |
| artifact_id | The unique identifier of the artifact (number, required) |
| get_job_logs | Get job logs |
| failed_only | When true, gets logs for all failed jobs in run_id (boolean, optional) |
| job_id | The unique identifier of the workflow job (required for single job logs) (number, optional) |
| return_content | Returns actual log content instead of URLs (boolean, optional) |
| get_workflow_run | Get workflow run |
| get_workflow_run_logs | Get workflow run logs |
| get_workflow_run_usage | Get workflow usage |
{
"mcpServers": {
"github": {
"url": "https://api.githubcopilot.com/mcp/"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GITHUB_PERSONAL_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| GITHUB_HOST | Endpoint or connection string the server talks to. | Optional |
| TOOL_ADD_ISSUE_COMMENT_DESCRIPTION | Configuration value read at startup. | Optional |
| TOOL_CREATE_BRANCH_DESCRIPTION | Configuration value read at startup. | Optional |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
A Model Context Protocol (MCP) server that enables AI assistants to integrate with Prometheus Alertmanager
Auth0 Model Context Protocol (MCP) Server (Beta) — A secure and extendable implementation of an MCP server that provides AI assistants with
Query Onchain data, like ERC20 tokens, transaction history, smart contract state.