Skip to content
Build Perch
Browse documentation

GitHub

Short answer: GitHub is the one integration built on GitHub’s own MCP server: connecting the GitHub tools runs a helper published by GitHub itself, locally on your machine. A personal access token is optional for basic search and required for code search or the MCP tools.

What makes GitHub different from the other integrations?

GitHub is the only integration that uses a Model Context Protocol (MCP) server: when you connect the GitHub tools, the app runs a helper published by GitHub itself, locally on your machine, and it adds extra GitHub tools on top of the built-in search. Gmail, Discord, and Notion connect straight to each service’s official API instead, with no separate helper.

How do I connect it?

Two layers: the token works on its own; the GitHub tools connection requires the token.

  1. Personal access token (optional). Create one on GitHub. A classic token is recommended over a fine-grained one, since fine-grained “select repos” tokens can silently under-return results and can’t read notifications. Scope it to public_repo (classic) or “Public repositories: Read” (fine-grained). Paste it into Integrations → GitHub. This alone raises the built-in search tool’s rate limit and turns on code search (no MCP connection required).
  2. Connect GitHub tools (needs the token). Click Connect GitHub tools in the same row to start the MCP server. It adds its own tools for reading pull requests, issues, and file contents, on top of code search, and reconnects automatically on future launches until you disconnect it.
  3. Make sure the External Research skill is on in the mode you use (it is on by default in modes like Assistant) so the AI can use search_github. The extra GitHub tools appear automatically once connected; there’s no separate skill to enable.

What can the AI do on GitHub?

With just a token: search_github, a built-in tool that searches code, issues, pull requests, or repositories (code search needs the token; issue/repo search works without one, just at a lower rate limit). With the MCP server connected: its own set of GitHub tools for reading pull requests, issues, and file contents, alongside code search.

Good to know

  • Without a token, search_github is capped at 10 searches/minute and code search is off; with one, it’s 30 searches/minute, code search works, and REST calls get a 5,000/hour budget.
  • Use a classic token if you can. Fine-grained “select repos” tokens are the newer option but under-return on search and can’t read notifications; a plain classic PAT is the more reliable choice for an individual account.
  • The token is write-only from the app’s side, like every other integration secret: the interface can replace or delete it, never read it back.
  • Disconnecting the MCP server keeps the token. You can turn off the richer GitHub tools without losing search_github’s rate-limit boost, and reconnect later.