Model Context Protocol
Use this data inside Claude
Commitgraph is a connector. Add the endpoint below and Claude can query 6,593 ranked developers across 88 countries and 119 cities directly — 12 tools, 5 ready-made prompts, and the same snapshot this site renders.
It is public and read-only. There is no account, no API key and no OAuth step, because there is nothing here to protect: one committed snapshot, served the same way to everybody.
Endpoint
https://top-github-users-amber.vercel.app/api/mcpClaude — web, desktop and mobile
A custom connector. Available on Free, Pro, Max, Team and Enterprise; Free accounts are limited to one.
- 01Open Settings, then Connectors.
- 02Choose Add custom connector.
- 03Paste the endpoint above. Leave the advanced OAuth fields empty.
- 04Connect. The 12 tools and 5 prompts appear under Commitgraph in the attachments menu.
Claude Code
One command, no configuration file.
claude mcp add --transport http commitgraph https://top-github-users-amber.vercel.app/api/mcpAdd --scope project to commit it to the repository you are in, so everyone working there gets the same server.
As a Claude Code plugin
The packaged version: the connector plus a skill that teaches Claude which tool answers what, and the four properties of this data that make an answer wrong if they are ignored.
/plugin marketplace add MAKaminski/Top-Github-Users
/plugin install commitgraph@commitgraphAny other MCP client
Streamable HTTP, JSON-RPC 2.0 over POST, protocol version 2025-06-18. Older clients are answered in their own version rather than being forced to upgrade.
{
"mcpServers": {
"commitgraph": {
"type": "http",
"url": "https://top-github-users-amber.vercel.app/api/mcp"
}
}
}What Claude can ask it
5 prompts package the common multi-tool sequences, so the first useful answer does not depend on knowing the tool names.
Orient me on this dataset
commitgraph_orient
Read the integration guide and the dataset description, then summarise what this data can and cannot answer. Run this once at the start of a session.
Report on a country or city
commitgraph_place_report
A briefing on one place: its ranked developers, how it compares to the worldwide distribution, and the employers concentrated there.
Scout developers by criteria
commitgraph_scout
Find developers matching a location, employer or activity floor, and summarise the shortlist with the coverage gaps stated.
Compare developers
commitgraph_compare
Put two to five developers side by side on contributions, followers, ranks and streaks.
Audit how a ranking was produced
commitgraph_audit_ranking
Trace one developer's numbers back to their provenance: what was measured, what was estimated, and which accounts were excluded from the board they appear on.
And 12 tools underneath
commitgraph_get_integration_guideDescribes what this server is, every tool it exposes, how to connect from Claude Code or any MCP client, what the data means, and where it is wrong. Call this first if you are a service deciding how to consume this dataset.commitgraph_describe_datasetThe dictionary of what is available: snapshot date and provenance, all counts and totals, every field with its meaning, and the complete list of valid scope ids. Call this before querying so you know what can be asked for.commitgraph_list_placesList countries and cities with their scope ids, ISO-2 code, region, developer count and contribution totals. Use this to discover valid ids before calling get_leaderboard.commitgraph_get_leaderboardA ranked board for a scope: 'worldwide', 'country:{id}' or 'city:{id}'. Ranked by contributions, ties broken on followers then login.commitgraph_search_developersFind developers by free text over login, name, company and location, combined with numeric and place filters. The primary retrieval tool.commitgraph_get_developerOne developer in full: contributions, ranks, contribution calendar, streaks and monthly totals. If the developer is ranked but has no stored profile record, the leaderboard row is returned with an explanation rather than an empty result.commitgraph_compare_developersTwo to five developers side by side on the same measures.commitgraph_get_organizationsOrganizations ranked by the combined contributions of tracked developers who name them in their profile — not by follower count. Drawn from a free-text company field.commitgraph_get_repositoriesThe repository board. Produced by the scheduled crawler; returns an explicit empty state until that has run, rather than placeholder rows.commitgraph_get_rank_historyRank movement across snapshots for a scope. Reports plainly when there are too few snapshots to plot rather than returning an empty series.commitgraph_get_statisticsAggregate distributions across the snapshot: contribution percentiles, the public/private split, per-region totals, and the log-log correlation between followers and contributions.commitgraph_get_flagged_accountsAccounts excluded from every ranking as automation — above 300,000 contributions in twelve months. Published rather than dropped silently so the rule can be audited.
What it will not do
The server reads one committed snapshot, generated 2026-08-02. It has no write surface, no credential store and no access to the machine calling it — nothing leaves your session except the tool arguments themselves. It cannot tell you anything about GitHub right now: for live repository state, use GitHub’s own API.
Every tool result carries the snapshot date and says which of its numbers were measured and which were derived. That distinction is the point of the whole project and it is documented on the methodology page.
Without an MCP client
The same snapshot is a REST API at /api/v1, described by an OpenAPI document. Machine discovery lives at /.well-known/mcp.json and /llms.txt. Everything is CORS-open and unauthenticated.
Running it yourself
The server, the crawler and this site are one repository. Point a client at http://localhost:3000/api/mcp after pnpm dev, or set COMMITGRAPH_MCP_URL to aim the plugin at your own deployment instead of top-github-users-amber.vercel.app.