Filesystem
MCP Servers
Read/write local files
Repos, issues, PRs, code search
API key
OAuth flow
HTTPS
Not supported
Browser calls
Unconfirmed
Status
Not yet checked
A starting template for GitHub. Replace ENDPOINT with the path from the official documentation, which we link above rather than guess at.
# Uses OAuth. Exchange your credentials for an access token first.
curl -s "https://github.com/ENDPOINT" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Accept: application/json"This API is served over plain HTTP. Browsers block HTTP requests made from an HTTPS page, so you will need a server-side call.
Aggregated from one public source (public-apis), then normalised and checked by us.
Report an issue with this listing ↗MCP Servers
Read/write local files
MCP Servers
IP geolocation, threat and timezone lookups for agents
Answered from what our own scheduled checks found, not from the provider's marketing.
GitHub is listed in our free catalogue, but it requires OAuth, so you will need to register before your first call. Providers frequently reserve higher limits and commercial use for paid plans.
GitHub uses OAuth rather than a simple key, so you register an application and complete an authorisation flow before making calls. That is more setup than a key, and it is why OAuth APIs are harder to try quickly.
We could not confirm CORS support for GitHub. Test it from a browser before relying on it client-side; if the request succeeds in curl but fails in the console, CORS is the reason.
No. GitHub was only reachable over plain HTTP when we checked. Browsers block HTTP requests made from an HTTPS page, so this will fail in production unless you call it from a server instead.