# How to connect GitHub to Grok Bot (no API keys)

> Connect GitHub to Grok Bot with ClawLink in one click — 846 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.

Web version: https://claw-link.dev/grokbot/github

Grok Bot runs on its own cloud computer, so most GitHub guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical GitHub setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real GitHub actions from chat with no auth, token refresh, or tool wiring to build yourself.

**Start here — paste this into Grok Bot to set up ClawLink:**

> Set up ClawLink for me and tell me when it's ready.
> 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login`
> 2. I'll approve it in my browser, then reply "approved".
> 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect github`
> 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready.

## Setup

It takes three steps to connect Grok Bot to GitHub.

1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints.
2. **Connect GitHub** — `npx -y @useclawlink/cli connect github`, then approve in the browser.
3. **Use it from chat** — ask Grok Bot in plain English.

**The same CLI works from any agent with shell access:**

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect github  # connect GitHub (browser OAuth)
npx -y @useclawlink/cli actions github  # list available actions
npx -y @useclawlink/cli run github <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval:

```bash
npx -y @useclawlink/cli login          # prints an approval link, approve it in your browser
npx -y @useclawlink/cli connect github
```

Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI.

Verify the connection by asking Grok Bot:

> Use GitHub to abort repository migration and walk me through the result in plain English.

### Using a different agent?

The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once GitHub is connected in the dashboard, that agent calls the same 846 GitHub tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## GitHub MCP for Grok Bot

Looking for a GitHub MCP server for Grok Bot? ClawLink connects GitHub to Grok Bot and exposes 846 GitHub tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) and the [Hermes GitHub integration](https://claw-link.dev/hermes/github) connect the same ClawLink account the same way.

## What the Grok Bot GitHub integration can do

846 GitHub tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 846.

### 30 of 846 GitHub tools for Grok Bot

| Tool | What it does |
|---|---|
| **Abort repository migration** `github_abort_repository_migration` | Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation. |
| **Accept repository invitation** `github_accept_repository_invitation` | Accepts a PENDING repository invitation that has been issued to the authenticated user. |
| **Add a repository collaborator** `github_add_a_repository_collaborator` | Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation… |
| **Add app access restrictions** `github_add_app_access_restrictions` | Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. |
| **Add assignees to an issue** `github_add_assignees_to_an_issue` | Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository. |
| **Add email address for authenticated user** `github_add_email_address_for_authenticated_user` | Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the… |
| **Add field to user project** `github_add_field_to_user_project` | Tool to add a custom field to a user-owned GitHub Projects V2 project. Use when you need to add fields like status, priority, or custom data to organize project items. |
| **Add item to user project** `github_add_item_to_user_project` | Tool to add an issue or pull request to a user-owned GitHub project. Use when you need to add existing repository items to a project board. |
| **Add labels to an issue** `github_add_labels_to_an_issue` | Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created. |
| **Add or update team membership for user** `github_add_or_update_team_membership_for_user` | Adds a GitHub user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no change is made. |
| **Add or update team project permissions** `github_add_or_update_team_project_permissions` | Adds a classic project to a team or updates the team's permission on it. This endpoint grants or updates permissions for a team on a specific classic project (not Projects V2). |
| **Add or update team repository permissions** `github_add_or_update_team_repository_permissions` | Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization. |
| **API root** `github_api_root` | Retrieves a map of all top-level GitHub REST API resource URLs and their templates |
| **Check if gist is starred** `github_check_if_gist_is_starred` | Checks if a gist is starred by the authenticated user |
| **Check if pull request has been merged** `github_check_if_pull_request_has_been_merged` | Checks if a specified GitHub pull request has been merged, indicated by a 204 HTTP status |
| **Check if user can be assigned** `github_check_if_user_can_be_assigned` | Verifies if a GitHub user can be assigned to issues in a repository; assignability is confirmed |
| **Check if user can be assigned to issue** `github_check_if_user_can_be_assigned_to_issue` | Checks if a specified GitHub user can be assigned to a given issue within a repository |
| **Check if user follows another user** `github_check_if_user_follows_another_user` | Checks if a GitHub user `username` follows `target_user`; returns a 204 HTTP status if true |
| **Check if user is blocked by authenticated user** `github_check_if_user_is_blocked_by_authenticated_user` | Checks if the specified GitHub user is blocked by the authenticated user; a 204 No Content |
| **Check if user is blocked by organization** `github_check_if_user_is_blocked_by_organization` | Checks if a GitHub user is blocked by an organization |
| **Check if user is repository collaborator** `github_check_if_user_is_repository_collaborator` | Checks if a user is a collaborator on a specified GitHub repository, returning a 204 status if |
| **Check person followed by auth user** `github_check_person_followed_by_auth_user` | Checks if the authenticated GitHub user follows a target GitHub user |
| **Check private vulnerability reporting status** `github_check_private_vulnerability_reporting_status` | Checks if private vulnerability reporting is enabled for the specified repository |
| **Check public organization membership for user** `github_check_public_organization_membership_for_user` | Check if a user is a public member of an organization |
| **Check team permissions for a project** `github_check_team_permissions_for_a_project` | Checks if a team has 'read', 'write', or 'admin' permissions for an organization's specific |
| **Check team permissions for a repository** `github_check_team_permissions_for_a_repository` | Checks a team's permissions for a specific repository within an organization, including |
| **Check token** `github_check_token` | Checks if a GitHub App or OAuth access_token is valid for the specified client_id and retrieves |
| **Compare two commits** `github_compare_two_commits` | Compares two commit points (commits, branches, tags, or SHAs) within a repository or across |
| **Create inference chat completions** `github_create_inference_chat_completions` | Create chat completions using GitHub Models inference API |
| **Create inference embeddings** `github_create_inference_embeddings` | Create inference embeddings using GitHub's AI models |

## Example prompts

**Abort Repository Migration**

> Use GitHub to abort repository migration and walk me through the result in plain English.

**Accept Repository Invitation**

> Use GitHub to accept repository invitation and walk me through the result in plain English.

**Add A Repository Collaborator**

> Use GitHub to add a repository collaborator and walk me through the result in plain English.

**Add App Access Restrictions**

> Use GitHub to add app access restrictions and walk me through the result in plain English.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want GitHub working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Connection flow** | Register a GitHub app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect GitHub through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for GitHub. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| **Agent usability** | You still need to expose the right GitHub actions to the runtime in a format your agent can reliably use. | 846 tools for GitHub are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes GitHub to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect GitHub in the browser, and the 846 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in.

### Connection succeeds but no tools appear
Reconnect GitHub from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

### "Tool schema not loaded yet" error when calling GitHub tools
GitHub tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every GitHub call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

### GitHub returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

### OAuth finished in the browser but the account is still missing
Try reconnecting GitHub and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

### Is there a Grok Bot GitHub integration?
Yes. ClawLink is the fastest way to connect Grok Bot to GitHub: link your GitHub account once in the browser and Grok Bot can call the GitHub API through 846 ready-made tools — no custom code or token handling.

### How do I connect GitHub to Grok Bot with ClawLink?
Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect github` to authorize GitHub. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage.

### How long does it take to connect GitHub to Grok Bot?
About two minutes. Sign in, click Connect next to GitHub in the dashboard, authenticate, and Grok Bot can use it from the next chat message.

### Why use ClawLink instead of wiring GitHub up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want GitHub working from chat.

### Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in.

## Related

- [PagerDuty](https://claw-link.dev/grokbot/pagerduty) — Manage incidents, on-call schedules, and services
- [SafetyCulture](https://claw-link.dev/grokbot/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.
- [Grok Bot LaunchDarkly integration](https://claw-link.dev/grokbot/launch-darkly) — A feature management platform that helps teams build better software faster using feature flags.