$ recombobulate _
home / tips / add-the-github-mcp-server-for-repository-automation
112

Add the GitHub MCP Server for Repository Automation

recombobulate @recombobulate · Mar 25, 2026 · MCP Servers
add-the-github-mcp-server-for-repository-automation

The GitHub MCP server turns Claude Code into a GitHub power user — reading issues, creating pull requests, checking CI status, and more, all without leaving your terminal.

// .claude/settings.json
{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_your_token_here"
      }
    }
  }
}

Once connected, you can work with your repositories conversationally:

"Summarise the open issues on this repo and group them by severity"

"Create a PR for the current branch with a description of what changed"

"Which CI check is failing on PR #47 and what does the error say?"

"Close all issues labelled 'wontfix' with a brief explanation comment"

You can combine it with git worktrees so Claude can make changes on a branch, then open a PR for its own work automatically. It's particularly powerful in agentic workflows where you want Claude to complete a full cycle from code to review-ready PR.

Generate a fine-grained personal access token scoped to just the repos you want Claude to access — don't hand it a token with write access to everything.

The GitHub MCP server collapses your dev workflow into a single conversation.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
125
Build a Custom MCP Server to Give Claude Direct Access to Your Internal Tools

MCP servers aren't just for third-party integrations — you can build your own to give Claude direct access to your internal tools, databases, APIs, and workflows. A custom MCP server turns any system your team uses into a tool Claude can call natively from your session.

recombobulate @recombobulate · 1 month ago
46
Scope MCP Servers to User, Project, or Enterprise Level So the Right Tools Appear in the Right Context

MCP servers can be scoped at three levels — user (available everywhere you work), project (shared with the team via version control), or enterprise (managed by your organization). Pick the right scope so each project gets exactly the tools it needs without cluttering unrelated ones.

recombobulate @recombobulate · 1 month ago
84
Use claude mcp to Add and Manage MCP Servers Without Editing JSON

Instead of manually editing settings JSON to add MCP servers, use the claude mcp command — add servers with one line, list what's configured, remove ones you don't need, and scope them to the right level, all from the terminal.

recombobulate @recombobulate · 1 month ago