GitHub integration: operations for AI agents
GitHub connects to Type.com as an integration. This page lists the 42 operations documented for Claude and Codex in Type.com: 24 read, 16 write, 2 destructive.
About GitHub
Browse code, commits and releases, work with issues and pull requests, review and merge PRs, and push changes in the repositories you connect, through GitHub's hosted MCP server.
Categories: Developer tools, Project management
How to connect GitHub to Type.com
- Connect
- Install the type.com GitHub App and sign in with GitHub (OAuth)
- Access
- Personal or shared: connect your own account or one shared workspace account.
To add the connection, follow the steps in Space connections.
Documented operations
42 operations. Your connection's permissions determine which operations are available.
42 operations listed.
- Read
Get commit
Get details for a commit from a GitHub repository
- Read
Get file contents
Get the contents of a file or directory from a GitHub repository
- Read
Get label
Get a specific label from a repository.
- Read
Get latest release
Get the latest release in a GitHub repository
- Read
Get release by tag
Get a specific release by its tag name in a GitHub repository
- Read
Get tag
Get details about a specific git tag in a GitHub repository
- Read
Issue read
Get information about a specific issue in a GitHub repository.
- Read
List branches
List branches in a GitHub repository
- Read
List commits
Get list of commits of a branch in a GitHub repository. Returns at least 30 results per page by default, but can return more if specified using the perPage parameter (up to 100).
- Read
List issue fields
List issue fields for a repository or organization. Returns field definitions including name, type (text, number, date, single_select), and for single_select fields the list of valid option names. When repo is omitted, returns org-level fields directly.
- Read
List issue types
List supported issue types for a repository or its owner organization. When repo is omitted, returns org-level issue types directly.
- Read
List issues
List issues in a GitHub repository. For pagination, use the 'endCursor' from the previous response's 'pageInfo' in the 'after' parameter.
- Read
List pull requests
List pull requests in a GitHub repository. If the user specifies an author, then DO NOT use this tool and use the search_pull_requests tool instead.
- Read
List releases
List releases in a GitHub repository
- Read
List repository collaborators
List collaborators of a GitHub repository. Results are paginated; the response includes `nextPage`, `prevPage`, `firstPage`, and `lastPage` fields. To get the next page, use the `nextPage` value as the `page` parameter.
- Read
List tags
List git tags in a GitHub repository
- Read
Pull request read
Get information on a specific pull request in GitHub repository.
- Read
Run secret scanning
Scan files, content, or recent changes for secrets such as API keys, passwords, tokens, and credentials. This tool is intended for targeted scans of specific files, snippets, or diffs provided directly as content. The files parameter accepts either a single string or an array of strings containing raw file contents or diff hunks, and returns detected secrets with their locations and related secret scanning metadata. Content must not be empty. For full repository scanning, other mechanisms are available. Caveats: - Only files within the codebase should be scanned. Files outside of the codebase should not be sent. - Files listed in .gitignore should be skipped.
- Read
Search code
Fast and precise code search across ALL GitHub repositories using GitHub's native search engine. Best for finding exact symbols, functions, classes, or specific code patterns.
- Read
Search commits
Search for commits across GitHub repositories using GitHub's commit search syntax. Useful for finding specific changes, authors, or messages across one or many repositories. Searches the default branch only.
- Read
Search issues
Search issues using natural-language semantic matching. Best for conceptual or paraphrased queries (e.g. "login fails after password reset"). Already scoped to is:issue.
- Read
Search pull requests
Search for pull requests in GitHub repositories using issues search syntax already scoped to is:pr
- Read
Search repositories
Find GitHub repositories by name, description, readme, topics, or other metadata. Perfect for discovering projects, finding examples, or locating specific repositories across GitHub.
- Read
Search users
Find GitHub users by username, real name, or other profile information. Useful for locating developers, contributors, or team members.
- Write
Add comment to pending review
Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure).
- Write
Add issue comment
Add a comment and/or reaction to a specific issue or issue comment in a GitHub repository. Use this tool with pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add or react to review comments. At least one of body or reaction is required.
- Write
Add reply to pull request comment
Add a reply and/or reaction to an existing pull request comment. This can create a new comment linked as a reply to the specified comment, add an emoji reaction to the specified comment, or do both. At least one of body or reaction is required.
- Write
Create branch
Create a new branch in a GitHub repository
- Write
Create or update file
Create or update a single file in a GitHub repository. If updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations. To obtain the current blob SHA before updating, call the get_file_contents tool with the same owner, repo, and path, and set its ref parameter to this tool's branch value. The first text result reports the blob SHA for the requested path. SHA MUST be provided for existing file updates.
- Write
Create pull request
Create a new pull request in a GitHub repository.
- Write
Create repository
Create a new GitHub repository in your account or specified organization
- Write
Fork repository
Fork a GitHub repository to your account or specified organization
- Write
Issue write
Create a new or update an existing issue in a GitHub repository.
- Write
Merge pull request
Merge a pull request in a GitHub repository.
- Write
Push files
Push multiple files to a GitHub repository in a single commit
- Write
Request copilot review
Request a GitHub Copilot code review for a pull request. Use this for automated feedback on pull requests, usually before requesting a human reviewer.
- Write
Sub issue write
Add a sub-issue to a parent issue in a GitHub repository.
- Write
Update issue comment
Update the body of an existing issue or pull request conversation comment. This tool cannot update pull request review comments.
- Write
Update pull request
Update an existing pull request in a GitHub repository.
- Write
Update pull request branch
Update the branch of a pull request with the latest changes from the base branch.
- Destructive
Delete file
Delete a file from a GitHub repository
- Destructive
Pull request review write
Create and/or submit, delete review of a pull request. Available methods: - create: Create a new review of a pull request. If "event" parameter is provided, the review is submitted. If "event" is omitted, a pending review is created. - submit_pending: Submit an existing pending review of a pull request. This requires that a pending review exists for the current user on the specified pull request. The "body" and "event" parameters are used when submitting the review. - delete_pending: Delete an existing pending review of a pull request. This requires that a pending review exists for the current user on the specified pull request. - resolve_thread: Resolve a review thread. Requires only "threadId" parameter with the thread's node ID (e.g., PRRT_kwDOxxx). The owner, repo, and pullNumber parameters are not used for this method. Resolving an already-resolved thread is a no-op. - unresolve_thread: Unresolve a previously resolved review thread. Requires only "threadId" parameter. The owner, repo, and pullNumber parameters are not used for this method. Unresolving an already-unresolved thread is a no-op.
No operations match.
Not supported
- Resources outside the connected GitHub App/user permissions and organization policies.
- Additional vendor APIs and toolsets outside the 42 listed tools require a connection that exposes them.
Example prompts
- List the open pull requests in our web repo that are waiting on my review.
- Open an issue in the api repo for the checkout timeout bug and assign it to me.
- Summarize what changed in the last 20 commits on main.
- Review PR #412 and leave comments on anything risky.
Get started
- Open Space settings → Connections and search for GitHub.
- Connect your account and add the connection to the Space.
- Ask for what you need in any thread in that Space.
See How connections work for access and permissions, or browse all integrations.
Reference date: October 28, 2026. GitHub API docs.