|
2 | 2 | "slug": "github", |
3 | 3 | "name": "GitHub", |
4 | 4 | "tagline": "Repos, issues, PRs, and Actions in every format agents speak.", |
5 | | - "description": "GitHub exposes more agent-callable surface area than almost any service: an official remote MCP server, a fully-specified REST API, a GraphQL API, and the `gh` CLI. Pick the format that fits your agent — they all reach the same data.", |
| 5 | + "description": "GitHub exposes more agent-callable surface area than almost any service: an official remote MCP server, a fully-specified REST API, a GraphQL API, and the `gh` CLI. Pick the format that fits your agent \u2014 they all reach the same data.", |
6 | 6 | "domain": "github.com", |
7 | 7 | "icon": "https://www.google.com/s2/favicons?domain=github.com&sz=64", |
8 | 8 | "categories": [ |
|
22 | 22 | "note": "Fine-grained PATs let you scope access per-repo and per-permission." |
23 | 23 | } |
24 | 24 | ], |
25 | | - "guide": "**Remote MCP (easiest):** point your client at `https://api.githubcopilot.com/mcp/`. Clients with OAuth support (VS Code 1.101+, Claude Code, Cursor) handle the consent flow automatically. For clients without OAuth, pass a PAT instead: `Authorization: Bearer <your-pat>`.\n\n**Personal access token:** create one under [Settings → Developer settings → Personal access tokens](https://github.com/settings/tokens). Prefer fine-grained tokens scoped to the repos and permissions your agent actually needs. Use it with REST and GraphQL:\n\n```bash\n# REST\ncurl https://api.github.com/user -H \"Authorization: Bearer $GITHUB_TOKEN\"\n\n# GraphQL\ncurl https://api.github.com/graphql \\\n -H \"Authorization: Bearer $GITHUB_TOKEN\" \\\n -d '{\"query\": \"{ viewer { login } }\"}'\n```\n\n**CLI:** `gh auth login` stores credentials in your keychain; agents running in your shell inherit them. This is often the lowest-friction path for coding agents.", |
| 25 | + "guide": "**Remote MCP (easiest):** point your client at `https://api.githubcopilot.com/mcp/`. Clients with OAuth support (VS Code 1.101+, Claude Code, Cursor) handle the consent flow automatically. For clients without OAuth, pass a PAT instead: `Authorization: Bearer <your-pat>`.\n\n**Personal access token:** create one under [Settings \u2192 Developer settings \u2192 Personal access tokens](https://github.com/settings/tokens). Prefer fine-grained tokens scoped to the repos and permissions your agent actually needs. Use it with REST and GraphQL:\n\n```bash\n# REST\ncurl https://api.github.com/user -H \"Authorization: Bearer $GITHUB_TOKEN\"\n\n# GraphQL\ncurl https://api.github.com/graphql \\\n -H \"Authorization: Bearer $GITHUB_TOKEN\" \\\n -d '{\"query\": \"{ viewer { login } }\"}'\n```\n\n**CLI:** `gh auth login` stores credentials in your keychain; agents running in your shell inherit them. This is often the lowest-friction path for coding agents.", |
26 | 26 | "sources": [ |
27 | 27 | { |
28 | | - "title": "github/github-mcp-server — remote server & PAT setup", |
| 28 | + "title": "github/github-mcp-server \u2014 remote server & PAT setup", |
29 | 29 | "url": "https://github.com/github/github-mcp-server" |
30 | 30 | }, |
31 | 31 | { |
32 | | - "title": "GitHub REST API — authenticating", |
| 32 | + "title": "GitHub REST API \u2014 authenticating", |
33 | 33 | "url": "https://docs.github.com/en/rest/authentication/authenticating-to-the-rest-api" |
34 | 34 | } |
35 | 35 | ], |
|
51 | 51 | "format": "openapi", |
52 | 52 | "name": "GitHub REST API", |
53 | 53 | "endpoint": "https://api.github.com", |
| 54 | + "spec": "https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json", |
54 | 55 | "specUrl": "https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json", |
55 | 56 | "auth": "token", |
56 | 57 | "authHeader": "Authorization: Bearer {pat}", |
|
0 commit comments