Developer Tools846 toolsBrowser login (OAuth), no API keys
GitHub integration for AI agents
Manage repositories, issues, pull requests, and workflows
Use it from your agent
One ClawLink account serves every agent you run. Pick the guide for yours, or connect GitHub once and call the same tools from all of them.
Deeper comparison, failure modes and setup details: GitHub for AI agents, in depth.
Setup
Connect github through ClawLink's hosted setup.
- Auth: Browser login (OAuth), no API keys. The credential stays on the ClawLink server; your agent holds only a ClawLink key you can revoke.
- Where: the ClawLink dashboard, or ask your agent to connect it.
What your agent can do
GitHub exposes 846 tools through ClawLink. The 30 most used are listed here; your agent sees all of them.
| Tool | What it does | Kind |
|---|---|---|
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. | Read |
github_accept_repository_invitation | Accepts a PENDING repository invitation that has been issued to the authenticated user. | Read |
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… | Write |
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. | Write |
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. | Write |
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… | Write |
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. | Write |
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. | Write |
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. | Write |
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. | Write |
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). | Write |
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. | Write |
github_api_root | Retrieves a map of all top-level GitHub REST API resource URLs and their templates | Read |
github_check_if_gist_is_starred | Checks if a gist is starred by the authenticated user | Read |
github_check_if_pull_request_has_been_merged | Checks if a specified GitHub pull request has been merged, indicated by a 204 HTTP status | Read |
github_check_if_user_can_be_assigned | Verifies if a GitHub user can be assigned to issues in a repository; assignability is confirmed | Read |
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 | Read |
github_check_if_user_follows_another_user | Checks if a GitHub user `username` follows `target_user`; returns a 204 HTTP status if true | Read |
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 | Read |
github_check_if_user_is_blocked_by_organization | Checks if a GitHub user is blocked by an organization | Read |
github_check_if_user_is_repository_collaborator | Checks if a user is a collaborator on a specified GitHub repository, returning a 204 status if | Read |
github_check_person_followed_by_auth_user | Checks if the authenticated GitHub user follows a target GitHub user | Read |
github_check_private_vulnerability_reporting_status | Checks if private vulnerability reporting is enabled for the specified repository | Read |
github_check_public_organization_membership_for_user | Check if a user is a public member of an organization | Read |
github_check_team_permissions_for_a_project | Checks if a team has 'read', 'write', or 'admin' permissions for an organization's specific | Read |
github_check_team_permissions_for_a_repository | Checks a team's permissions for a specific repository within an organization, including | Read |
github_check_token | Checks if a GitHub App or OAuth access_token is valid for the specified client_id and retrieves | Read |
github_compare_two_commits | Compares two commit points (commits, branches, tags, or SHAs) within a repository or across | Read |
github_create_inference_chat_completions | Create chat completions using GitHub Models inference API | Write |
github_create_inference_embeddings | Create inference embeddings using GitHub's AI models | Write |