GitHub repos, PRs, issues, branches, code search via GitHub's official hosted MCP
Use with AI AssistantsMCP
Connect Claude, Cursor, or any MCP-compatible client — then call tools directly
① Add This MCP Server
Paste into your AI client config — then all its tools are available instantly.
{
"mcpServers": {
"github-api": {
"url": "https://mcp.aerostack.dev/s/aerostack/mcp-github",
"headers": {
"Authorization": "Bearer YOUR_AEROSTACK_TOKEN"
}
}
}
}Replace YOUR_AEROSTACK_TOKEN with your API token from the dashboard.
② Call a Tool
Ask your AI assistant to call a specific tool, or send raw JSON-RPC:
Natural Language Prompt
“Use the list_repos tool to list repositories for the authenticated user or a specified organization, with sorting and filtering options”
Using a Workspace?
Add this MCP to your Workspace — your team shares one token, secrets are stored securely, and every AI agent in the workspace can call it without per-user setup.
Official proxy MCP — GitHub repos, PRs, issues, branches, code search via GitHub's official hosted MCP
Live endpoint: https://mcp.aerostack.dev/s/aerostack/mcp-github
GitHub API is a proxy MCP server that forwards requests directly to the official GitHub MCP endpoint at https://api.githubcopilot.com/mcp/. All tools are maintained by GitHub — new tools are available immediately without any Aerostack update.
Type: Proxy (hosted by GitHub)
Auth: Bearer token via GITHUB_PERSONAL_ACCESS_TOKEN
| Variable | Required | Description | How to Get |
|---|---|---|---|
GITHUB_PERSONAL_ACCESS_TOKEN | Yes | GitHub Personal Access Token with required scopes | github.com → Settings → Developer settings → Personal access tokens → Generate new token |
GITHUB_PERSONAL_ACCESS_TOKEN when prompted — stored encrypted, injected automaticallyOnce added, every AI agent in your workspace can use GitHub tools automatically.
"List all my GitHub items and summarize the most recent ones"
"Find anything related to [keyword] in GitHub"
"Create a new entry with the following details: ..."
curl -X POST https://mcp.aerostack.dev/s/aerostack/mcp-github \
-H 'Content-Type: application/json' \
-H 'X-Mcp-Secret-GITHUB-PERSONAL-ACCESS-TOKEN: your-key' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_repos","arguments":{}}}'
MIT
@aerostack
Pre-built functions for the most common MCP tool patterns. Clone, extend, and deploy.
by @aerostack
Tasks, projects, sections, comments, teams, custom fields via Asana's official MCP
by @aerostack
Jira issues, sprints, Confluence pages via Atlassian's official MCP
by @aerostack
Cloudflare Workers, KV, R2, D1, Pages, DNS via Cloudflare's official MCP
by @aerostack
Dashboards, monitors, logs, metrics, incidents, SLOs, APM traces via Datadog's official MCP
by @aerostack
Files, frames, components, comments, variables via Figma's official MCP
by @aerostack
Dashboards, alerting, Loki logs, Tempo traces, Prometheus metrics via Grafana's official MCP
Yes. The search_code tool lets Claude run GitHub code search queries against any repo you have access to, returning matching file paths, line numbers, and snippets — no local clone needed.
It uses a stored GitHub token (classic PAT or fine-grained). You configure it once in Aerostack; Claude then calls list_repos, create_issue, and list_pull_requests using that token on every request.
The list_pull_requests tool returns PR metadata including state, head/base refs, and labels. For full diff content you'd pair it with get_repo to locate the compare URL — raw diff retrieval depends on GitHub API scope granted.
Yes. list_repos accepts search parameters and get_repo fetches a single repo by owner/name. Claude can loop over results and filter by language, topic, or visibility without loading every repo at once.