FastMCP FastMCP
Sign In
G

GitHub

Manage repositories, issues, and search code via GitHub API.

3 views
0 installs
Updated Dec 25, 2025
Not audited
API Development Developer Tools
Manage repositories, issues, and search code via GitHub API.

  1. Sign in to GitHub
    Open https://github.com and sign in with the account that should be used by the MCP server. (docs.github.com)

  2. Open Developer settings → Personal access tokens
    Click your profile photo → Settings → Developer settings → Personal access tokens. Choose either "Fine‑grained tokens" or "Tokens (classic)" depending on your needs. (Fine‑grained tokens are recommended when you want to limit access to specific repos; classic tokens use broad scopes like repo.) (docs.github.com)

  3. Generate a new token

    • For a classic token: click "Tokens (classic)" → "Generate new token (classic)".
      Select an expiration (recommended) and check the repo scope if you need repository read/write access (or public_repo for only public repos). (docs.github.com)
    • For a fine‑grained token: click "Fine‑grained tokens" → "Generate new token".
      Select the resource owner, pick the specific repositories (or repo access level) and grant the minimal repository permissions required (for file operations you typically need repository "Contents" read & write and any additional permissions your workflow needs). (github.blog)

  4. Name the token and set an expiration
    Give the token a descriptive name (e.g., "FastMCP – GitHub MCP") and set an expiration consistent with your security policy (shorter is safer). (docs.github.com)

  5. Create and copy the token (copy now — it’s shown only once)
    Click Generate / Create. When GitHub displays the token string, copy it immediately to your clipboard or password manager — GitHub will not show the full token again after you leave the page. (docs.github.com)

  6. Click your "Install Now" / FastMCP button and paste the token into the FastMCP connection interface
    When the FastMCP connection/install dialog appears (the "Install Now" prompt), you will see a field labeled like "GitHub Personal Access Token" (or an env var GITHUB_PERSONAL_ACCESS_TOKEN). Paste the copied token into that field and submit to save the connection. The MCP server will use that value as the GITHUB_PERSONAL_ACCESS_TOKEN environment variable. (This is the place where the README’s "<YOUR_TOKEN>" belongs.) (docs.github.com)

  7. Verify the connection
    After installing, run a simple read operation (e.g., list a repository’s files or fetch repo metadata) from the MCP interface to confirm the token has the required access. If you get permission errors, adjust the token’s scopes/permissions or create a new token with the needed permissions. (docs.github.com)

  8. Secure and rotate the token
    Store the token in a secure password manager. If the token is compromised, delete/revoke it from Developer settings and generate a replacement. Consider periodically rotating tokens and using fine‑grained tokens with minimal permissions where possible. If your organization enforces token policies, you may need administrator approval for fine‑grained tokens. (docs.github.com)

Quick Start

View on GitHub

More for API Development

View All →

More for Developer Tools

View All →

Similar MCP Servers

Report Issue

Thank you! Your issue report has been submitted successfully.