Connect GitHub to Claude via Bindify

Set up once. Never re-authenticate again.

// Why use Bindify for GitHub?

GitHub App installation tokens expire in just 1 hour. Refresh token rotation is single-use, and race conditions cause silent failures that kill your session mid-workflow. Bindify handles GitHub's complex token lifecycle so you never lose your connection. Learn more about MCP connection problems →

// Setup steps

Step 1: Sign up

Create a Bindify account at app.bindify.dev. You can start with the free 24-hour trial — no credit card required.

Step 2: Connect GitHub

In your Bindify dashboard, click "Add Connection" and select GitHub. You will be redirected to GitHub to authorize Bindify. Choose which repositories and organizations to grant access to.

Step 3: Copy your secret URL

After authorization, Bindify generates your permanent MCP URL. Copy it from the dashboard. It looks like:

https://api.bindify.dev/mcp/github/{your-credentials}/sse

Step 4: Add to Claude

Follow the instructions below for your Claude client.

// Claude Desktop

Open your Claude Desktop config file and add the GitHub MCP server:

{
  "mcpServers": {
    "github": {
      "url": "https://api.bindify.dev/mcp/github/{your-credentials}/sse"
    }
  }
}

Replace {your-credentials} with the value from your Bindify dashboard. Restart Claude Desktop to activate.

// Claude Code

Add the GitHub MCP server using the Claude Code CLI:

claude mcp add github \
  --transport http \
  --url https://api.bindify.dev/mcp/github/{your-credentials}

Replace {your-credentials} with the value from your Bindify dashboard.

// Troubleshooting

Claude says it cannot connect to GitHub
Check your Bindify dashboard. If the GitHub connection shows an error status, click "Re-authorize" to refresh the OAuth token. Your secret URL stays the same.
Cannot access a specific repository
GitHub's OAuth flow lets you control repository access. Revoke the connection and reconnect, granting access to the additional repositories during the GitHub authorization step.
Getting 401 Unauthorized errors
This typically means the GitHub token has expired and automatic refresh failed. Click "Re-authorize" in your Bindify dashboard to fix this immediately.
I want to check my connection status
Log in to app.bindify.dev and view your dashboard. Each connection shows its status (active, refreshing, or error) and last-used timestamp.
Do I need to rotate my connection?
OAuth connections with managed refresh renew automatically — no rotation needed. If you connected using an API key or client-side keys, you must rotate annually for security. Click "Re-authorize" in your dashboard before the 1-year mark.