GitHub Repo Analytics MCP — Stars, Commits & Languages, No PAT

Give an AI agent read-only analytics on any public GitHub repo without minting a personal access token. This Model Context Protocol server runs on Apify's proxy pool, so Claude, Cursor, or any MCP client can pull repository stats, search repos by topic, break down language composition, and compare repos side by side as structured JSON — no PAT to manage, no rate-limit juggling. It is a complement to GitHub's official MCP (which requires auth), aimed at no-auth public-repo intelligence and trend tracking.

What this MCP server does

GitHub's own MCP server requires a personal access token and inherits its 5,000-request/hour rate cap. This server is built for the opposite use case: read-only analytics on public repositories with zero auth setup. An agent discovers the tools, calls them with structured parameters, and gets clean JSON back — ready to reason over in a multi-step chain.

Tools exposed via MCP

This server exposes four tools:

• get_repo_stats — detailed stats for one repository (owner, repo): stars, forks, open issues, and activity.
• search_repos — search repositories by query, with optional sort (stars, forks, or updated) and max_results. Returns names, descriptions, stars, and forks.
• get_repo_languages — language composition breakdown for a repository (owner, repo).
• compare_repos — compare a list of repositories (repos: list of owner/repo strings) head to head.

Each tool returns clean structured JSON the agent can parse and chain across calls.

Why this beats building your own Octokit wrapper

Feature	NexGenData GitHub Analytics MCP	GitHub Official MCP	Octokit / GraphQL custom	Generic LLM (no tools)
MCP-native	Yes	Yes	No	No tools
No GitHub PAT required for public data	Yes — Apify proxy pool	No — PAT required	PAT required	N/A
Repo stats: stars, forks, issues	Yes	Yes	Build it yourself	Hallucinated
Repo search by topic	Yes	Yes	Build it yourself	None
Language composition breakdown	Yes	Limited	Build it yourself	None
Cross-repo comparison	Yes	Limited	Build it yourself	None
Auth	Apify token (no GitHub PAT)	GitHub PAT required	GitHub PAT	None

This is read-only public-repo analytics. It does not create issues or PRs — for write operations use GitHub's official MCP.

Use cases

• OSS trend tracking — star and fork velocity across a watchlist of repos.
• Due-diligence agent — assess a project's activity and contributor health before adopting it.
• Competitive OSS intel — compare_repos to benchmark rivals on stars, forks, and activity.
• Dev-tool market research — search_repos to surface trending projects in a topic without a PAT.
• Newsletter / report automation — auto-summarize weekly repo activity for a digest.

Connect to Claude Desktop

{
  "mcpServers": {
    "nexgendata-github": {
      "url": "https://nexgendata--github-mcp-server.apify.actor/mcp",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}

Sample call and response

Get stats for a repository:

{
  "name": "get_repo_stats",
  "arguments": { "owner": "facebook", "repo": "react" }
}

{
  "text": "Retrieved stats for facebook/react",
  "structuredContent": {
    "repo": "facebook/react",
    "data": [
      {
        "fullName": "facebook/react",
        "stars": 228000,
        "forks": 46500,
        "openIssues": 950,
        "defaultBranch": "main",
        "lastPushed": "2026-06-28"
      }
    ]
  }
}

FAQ

Do I need a GitHub personal access token? No — for public repository data this server uses Apify's proxy pool, so no PAT is required.

How is this different from GitHub's official MCP server? GitHub's official server requires authentication and supports read/write. This is no-auth, read-only analytics on public repos, hosted on Apify — aimed at trend tracking and due diligence rather than repo management.

Which MCP clients work? Any MCP-compatible client — Claude Desktop, Cursor, Cline, and custom agents using the official MCP SDKs.

Can it create issues or PRs? No — it is read-only analytics by design. Use GitHub's official MCP for write operations.

Do I need separate API keys? No — only your Apify API token to connect.

Related NexGenData MCP servers & developer-tools actors

Use case	Actor
Developer tools MCP (NPM, PyPI, Stack Overflow)	developer-tools-mcp-server
Web-scraping MCP (any URL, AI agents)	web-scraping-mcp-server
SEO & web analysis MCP	seo-web-analysis-mcp-server
Domain intelligence MCP	domain-intelligence-mcp-server
News MCP (Hacker News + tech press)	news-mcp-server
Reddit MCP (r/programming, r/MachineLearning)	reddit-mcp-server
YouTube / media MCP (DevRel videos)	youtube-media-mcp-server
Academic research MCP (arxiv + papers)	academic-research-mcp-server
26-server gateway (GitHub + 25 more)	enterprise-mcp-gateway

---

Built and maintained by NexGenData. Home: thenextgennexus.com