{
  "markdown": "# GitHub Repository Intelligence MCP Server\n\nA hosted [Model Context Protocol](https://modelcontextprotocol.io) server that gives AI coding agents structured intelligence about any GitHub repository — overview, recent PRs, contributors, hot files, CI status, and dependencies — through a single MCP endpoint.\n\n**No local setup. No `git clone`. No Octokit boilerplate.** Plug your agent into the MCP URL and start asking questions.\n\n## Why this exists\n\nLocal GitHub MCP servers exist, but they require every user to set up Node/Python, install the server, manage tokens, and keep it patched. This Actor runs on Apify's platform and is reachable as a hosted streamable-HTTP MCP endpoint — your agent just needs the URL.\n\nIt's useful when you want an LLM to reason about a codebase without giving it filesystem or shell access: think code-review bots, repo-onboarding helpers, dependency-audit agents, refactor planners.\n\n### Hosted vs local — when this saves you time\n\n| | This Actor | Local MCP server |\n|---|---|---|\n| Setup | Paste URL + token into client config | `git clone`, install deps, manage Node/Python versions |\n| Distribution | Same URL works for every teammate | Each teammate sets up their own |\n| Updates | Always latest server build | You patch + redeploy |\n| Auth surface | One Apify token + optional GitHub PAT in tool args | GitHub PAT lives on every machine |\n| Cost when idle | $0 (Standby mode, billed per call) | Whatever your laptop/server costs |\n| When local wins | Air-gapped repos, on-prem GitHub Enterprise | — |\n\n### Three workflows it shortens\n\n1. **Repo onboarding** — drop the URL into Claude Code, ask *\"give me a one-page brief on `kubernetes/kubernetes`: maintainers, top 10 hot files, current PR pipeline, CI health.\"* One conversation, six tool calls, no clones.\n2. **PR-review prep** — before reviewing a stranger's PR, run `get_contributors` + `list_recent_prs` + `get_hot_files` on the target repo to know who you're dealing with and where the churn actually lives.\n3. **Dependency / supply-chain audit** — `get_dependencies` across a list of repos in a loop, no shell access required, no risk of malicious `npm install` running on your machine.\n\n## Tools exposed\n\n| Tool | What it returns | Typical use |\n|---|---|---|\n| `get_repo_overview` | Stars, forks, language, license, topics, last push | \"Is this repo still maintained?\" |\n| `list_recent_prs` | Recent PRs with author, state, merge dates | \"Show me the last 20 merged PRs by user X\" |\n| `get_contributors` | Top contributors by commit count | \"Who maintains this project?\" |\n| `get_hot_files` | Most-modified files over the last N commits | \"Where's the churn?\" |\n| `get_ci_status` | Check runs and conclusions for a ref | \"Is the default branch green?\" |\n| `get_dependencies` | Parses `package.json`, `requirements.txt`, `go.mod`, `Cargo.toml`, `pyproject.toml` | \"What does this project depend on?\" |\n\nEvery tool accepts an optional `github_token` parameter. With no token you get GitHub's 60-req/hour limit on public repos. Provide a fine-grained PAT and you get 5,000 req/hour and can access private repos.\n\n## Pricing\n\n**$0.005 per tool call. First 100 calls free per user.**\n\nPay-per-event model — you only pay when a tool actually executes. No subscription, no minimums. The server runs in Apify Standby mode, so you're not billed for idle time.\n\n## Usage\n\n### From an MCP-aware client (Claude Desktop, Cursor, Continue, etc.)\n\nThe Actor exposes a Streamable-HTTP MCP transport at:\n\n```\nhttps://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp\n```\n\nAuthentication uses your Apify token via the `Authorization: Bearer <APIFY_TOKEN>` header — most MCP clients let you configure this in their server config.\n\n### Example tool call (raw JSON-RPC)\n\n```bash\ncurl -X POST https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp \\\n  -H \"Authorization: Bearer <APIFY_TOKEN>\" \\\n  -H \"Content-Type: application/json\" \\\n  -H \"Accept: application/json, text/event-stream\" \\\n  -d '{\n    \"jsonrpc\": \"2.0\",\n    \"id\": 1,\n    \"method\": \"tools/call\",\n    \"params\": {\n      \"name\": \"get_repo_overview\",\n      \"arguments\": {\"owner\": \"facebook\", \"repo\": \"react\"}\n    }\n  }'\n```\n\n### From Claude Desktop config\n\n```json\n{\n  \"mcpServers\": {\n    \"github-repo-intel\": {\n      \"url\": \"https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp\",\n      \"headers\": {\n        \"Authorization\": \"Bearer <APIFY_TOKEN>\"\n      }\n    }\n  }\n}\n```\n\n## Limits and caveats\n\n- Free tier on Apify gets you $5/month of usage credits — enough for ~1,000 free tool calls before the per-event price kicks in.\n- The `get_hot_files` tool scans up to 200 commits and makes one API call per commit, so it eats GitHub rate limit the fastest. Pass a `github_token` if you call it often.\n- `get_ci_status` reads the GitHub **Checks API** — it surfaces GitHub Actions, CodeQL, and any third-party check that posts back via the Checks API. Repos that run their CI entirely on **external systems** (Prow, Buildkite, CircleCI without GitHub integration) may show 0 check runs even when the build is green. The response includes a `note` field flagging this case.\n- This is a **read-only** server. It cannot create PRs, comment on issues, or modify any repository state.\n- All data comes straight from the GitHub REST API — no caching layer, so freshness equals what the GitHub API returns.\n\n## Source & roadmap\n\nAuthor: [luongnp](https://github.com/luongnp). Open to feature requests — file an issue on the Actor page if you want a tool added (issues board, releases, dependency vulnerabilities via Dependabot API, etc.).\n",
  "bytes": 5571,
  "sha": "c5d73761f459c05043d165ac377a00a2364159339fad543a483aa7e37a7da72a",
  "repo_slug": "heisencodex-jpg/github-repo-intel-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_heisencodex_jpg_github_repo_in_c68ee92a/readme"
}