// MCP TOOL REFERENCE

GITHUB API MCP SERVER TOOLS

17 tools from the GitHub API MCP Server MCP Server, categorised by risk level.

READ TOOLS

get_file_contents Get the contents of a file or directory from a GitHub repository get_issue Get details of a specific issue in a GitHub repository. list_commits Get list of commits of a branch in a GitHub repository list_issues List issues in a GitHub repository with filtering options search_code Search for code across GitHub repositories search_issues Search for issues and pull requests across GitHub repositories search_repositories Search for GitHub repositories search_users Search for users on GitHub

WRITE TOOLS

add_issue_comment Add a comment to an existing issue create_branch Create a new branch in a GitHub repository create_issue Create a new issue in a GitHub repository create_or_update_file Create or update a single file in a GitHub repository create_pull_request Create a new pull request in a GitHub repository create_repository Create a new GitHub repository in your account fork_repository Fork a GitHub repository to your account or specified organization push_files Push multiple files to a GitHub repository in a single commit update_issue Update an existing issue in a GitHub repository

// FAQ

How many tools does the GitHub API MCP Server MCP server have? +

The GitHub API MCP Server MCP server exposes 17 tools across 2 categories: Read, Write.

How do I enforce policies on GitHub API MCP Server tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the GitHub API MCP Server server.

What risk categories do GitHub API MCP Server tools fall into? +

GitHub API MCP Server tools are categorised as Read (8), Write (9). Each category has a recommended default policy.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

GET STARTED →