integration · github

Claude + GitHub — full API, zero SDK.

Q: What scopes does wmcp.sh's GitHub OAuth grant?

Sign-in flow requests read:user user:email repo gist read:org workflow — covers repo CRUD, gists, org info, and workflow runs. The scope set is a union of sign-in and connector scopes so one OAuth round serves both.

Q: Tool count is too high (~900) — how to narrow?

Filter client-side by name prefix or tag. tools.filter(t => t.name.startsWith("issues")) for Issues only, etc. Most agent frameworks struggle past ~50 tools in a single message; filtering is essential.

GitHub publishes a canonical OpenAPI 3 spec covering every REST endpoint. wmcp.sh ingests it and serves you ~900 MCP tools, with your GitHub OAuth token auto-injected from the wmcp.sh sign-in. Same flow for Octokit alternatives, gh CLI scripts, and Composio replacements.

Last updated 2026-05-28 · works with Claude, OpenAI, LangChain, and any MCP client

Positioning

vs. the alternatives

Capability	Octokit / gh CLI	Composio GitHub	wmcp.sh
Setup time	Install SDK + token wiring	Platform signup + auth flow	Sign in with GitHub — done
Coverage	SDK reflects current GitHub API version	Curated common ops	Every documented endpoint (~900)
New endpoints	Wait for SDK release	Wait for platform update	Available the moment GitHub publishes
Auth	PAT or app token, you store it	OAuth via Composio platform	GitHub OAuth from wmcp.sh sign-in
MCP shape	Wrap each method yourself	Auto-mapped	Native MCP / tool_use
Cost	Free SDK + your hosting	Platform tier	Free 100/day + $29/mo Pro

What you get

Tools your agent calls

All MCP-shaped — consumed directly by Claude tool_use, OpenAI function-calling, or LangChain.

Tool	Type	Returns
`repos/getRepo`	Live action	Repo metadata + stats
`issues/createIssue`	Live action	Created issue with number + URL
`issues/listForRepo`	Live action	Open issue list (paginated)
`pulls/list`	Live action	PRs with state, base/head, mergeable status
`pulls/createPullRequest`	Live action	New PR with number + URL
`gists/createGist`	Live action	Gist URL
`actions/listWorkflowRuns`	Live action	CI run history
`search/code`	Live action	Code search results

Integrate

Python — agent files an issue

from wmcp import WmcpClient
from wmcp.anthropic import to_anthropic_tools, execute_tool_use
from anthropic import Anthropic

client = WmcpClient(api_key="webmcp_live_…")
spec   = "https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json"
tools  = client.tools(spec)

# 900+ tools is too many. Filter to Issues subset.
issue_tools = [t for t in tools if t.name.lower().startswith("issues")]

anthropic = Anthropic()
msg = anthropic.messages.create(
    model="claude-opus-4-7",
    max_tokens=1024,
    tools=to_anthropic_tools(issue_tools),
    messages=[{"role": "user",
               "content": "File a bug in New1Direction/webmcp-anything: '/u/<hash> returns 500 on cold cache'."}],
)

for block in msg.content:
    if block.type == "tool_use":
        # Worker auto-injects your signed-in GitHub OAuth token. Agent passes no auth.
        result = execute_tool_use(client, spec, block.model_dump())
        print(result)

FAQ

Frequently asked

Do I need a Personal Access Token?

No. If you've signed in to wmcp.sh with GitHub OAuth (the dashboard sign-in flow), your token is already stored and auto-injected on every api.github.com call. PATs still work if you prefer — pass via _auth arg.

What scopes does wmcp.sh's GitHub OAuth grant?

Sign-in flow requests read:user user:email repo gist read:org workflow — covers repo CRUD, gists, org info, and workflow runs. The scope set is a union of sign-in and connector scopes so one OAuth round serves both.

How does this differ from Composio's GitHub connector?

Composio maintains a curated set of operations. wmcp.sh ingests the canonical OpenAPI spec — every endpoint available, including newly-shipped ones, with zero version lag. Composio wins on per-customer auth UX; wmcp wins on completeness.

Tool count is too high (~900) — how to narrow?

Filter client-side by name prefix or tag. tools.filter(t => t.name.startsWith("issues")) for Issues only, etc. Most agent frameworks struggle past ~50 tools in a single message; filtering is essential.

Can I use GitHub Apps instead of OAuth Apps?

Not in v0 — wmcp.sh's GitHub provider is registered as an OAuth App. GitHub Apps (installation tokens) need their own auth flow; raise an issue if your use case needs it.

API agent-readiness

GitHub's the canonical OpenAPI-as-MCP example. If you're building your own API, see how to ship a clean spec + agent-friendly auth.

→ /agent-ready/api · cornerstone · done-for-you ($499+)

Need this done for you?

Skip the wiring — we build, deploy, and monitor.

Custom adapter + hosted MCP at mcp.yourbrand.com + verified badge. From $499 one-time setup.

See /managed → Submit (free)