Developer Tools

Connect GitHub to your AI agent

Yes — ClawLink is a hosted GitHub MCP server. 846 tools your agent can call from chat, with one-click hosted OAuth and nothing to run locally.

ClawLink hosts a managed GitHub MCP server that exposes 846 tools to your AI agent. You connect GitHub in one click, and your agent can read, create, and update GitHub data from chat without you building or running a local MCP server.

  • 846 tools callable from chat
  • One-click hosted OAuth
  • Works with OpenClaw, Hermes, Claude Code, Cursor, Codex, and any MCP client
  • No local server or config files
Claude
Claude
ClawLink
ClawLink
GitHub
GitHub

846 GitHub tools callable from any of them.

Setup

Three steps. About two minutes.

  1. 1

    Install ClawLink

    Add the plugin to your agent once.

  2. 2

    Connect GitHub

    One-click hosted OAuth in the dashboard.

  3. 3

    Use it from chat

    Ask your agent in plain English.

GitHub uses OAuth. You connect it in the browser: click Connect, sign in, approve. ClawLink stores the token and refreshes it on its own. You never touch a key or wire up a redirect URL.

bash
$npx -y @useclawlink/cli login
$npx -y @useclawlink/cli connect github

Run these in your terminal. The first opens a browser to sign in to ClawLink; the second opens a browser to authorize GitHub. No API keys to create or paste. Works with any agent that runs shell commands: OpenClaw, Hermes, Claude Code, Cursor, Codex, Cline, and more.

Use cases

What you can do with GitHub from chat

Work without tab-switching

Pull up GitHub issues, repos, tasks, or alerts without leaving the conversation.

Ship the routine stuff faster

The agent grabs GitHub context, drafts the next step, and runs the common maintenance actions.

Debug with real data

Ask for the current state from GitHub before the agent suggests a fix. No guessing.

Capabilities

The GitHub actions your agent can call

846 GitHub tools, ready the moment you connect.

  • Abort repository migration
  • Accept repository invitation
  • Add a repository collaborator
  • Add app access restrictions
  • Add assignees to an issue
  • Add email address for authenticated user
  • Add field to user project
  • Add item to user project
  • Add labels to an issue
  • Add or update team membership for user
  • Add or update team project permissions
  • Add or update team repository permissions

+ 834 more GitHub tools after you connect.

Examples

Ask in plain English

These map to real tool calls ClawLink makes against your connected account.

Abort repository migration

Use GitHub to abort repository migration and walk me through it.

Accept repository invitation

Use GitHub to accept repository invitation and walk me through it.

Add a repository collaborator

Use GitHub to add a repository collaborator and walk me through it.

Add app access restrictions

Use GitHub to add app access restrictions and walk me through it.

ClawLink vs DIY

Building the GitHub integration yourself, or hosting it?

 
DIY
ClawLink
Connection
Build it yourself. You register a developer app with GitHub, set up redirect URLs, handle the consent screen, store and refresh access tokens, and redo the wiring when scopes change.
Hosted hosted OAuth. Connect once in the browser. ClawLink owns the lifecycle.
Maintenance
Token refresh, permission debugging, env config, every edge case. All yours.
ClawLink handles the plumbing. You focus on the workflow.
Time to first call
Days to weeks. Auth, storage, tool wiring, testing. Then the agent can act.
About two minutes from sign-up to the agent calling GitHub.

FAQ

Quick questions

How do I connect GitHub to my AI agent?

Install ClawLink, open the dashboard, click Connect next to GitHub, and finish the hosted OAuth flow. Your agent can call GitHub from the next message. Two minutes, total.

Is there a GitHub MCP server I can use?

Yes. ClawLink exposes GitHub as 846 tools your agent calls through a hosted MCP-compatible runtime. You don't run a local server or edit a config file. The tools are there the moment you connect.

Do I need GitHub API credentials?

No separate API key. You sign in to GitHub through the normal OAuth flow and ClawLink handles the token after that.

How much does it cost?

Your first integration is free, plus a 7-day trial of the full catalog. Paid plans unlock the rest of the library.

Can I set this up from the terminal instead of the dashboard?

Yes. Run npx -y @useclawlink/cli login, then npx -y @useclawlink/cli connect github. The first opens a browser to sign in to ClawLink. The second opens a browser to authorize GitHub. No API keys to create. Works with OpenClaw, Hermes, Claude Code, Cursor, Codex, and any agent that runs shell commands.

Related

More Developer Tools integrations

Ready to connect GitHub?

First integration is free. No credit card.

Connect GitHub