GitHub Plugin for Claude Code
The plugin connects Claude Code to the platform's official remote MCP server. The checked-in configuration uses a personal access token, and the effective capability depends on that token, repository and organization access, selected toolsets, and policy. It can bring repository, issue, pull-request, code-review, and Actions context into an agent workflow without implying that every API operation is enabled by default.
Work with Repositories, Issues, and Pull Requests in Claude Code
Plugin quick facts
| Item | Detail |
|---|---|
| Marketplace name | github |
| Tool source | Official GitHub MCP server |
| Install target | github@claude-plugins-official |
| Authentication | Use the connection method presented by the installed plugin |
| First check | Read one issue or pull request in an allowed repository |
| Documentation reviewed | September 16, 2026 |
Setup and first check
Install the GitHub marketplace entry and authenticate only to the repositories required for the task:
/plugin install github@claude-plugins-officialInspect the active MCP tools after connection. A personal access token is one configuration path, not the only possible path across every environment. Start by retrieving one known issue or pull request, then confirm repository identity and write permissions before asking Claude Code to comment, label, merge, or change workflow state.
Coding work often starts outside the local checkout: an issue defines the request, a pull request contains the discussion, or an Actions run shows the failure. The plugin can let Claude Code retrieve that context and connect it to implementation decisions.
The MCP server exposes capabilities through toolsets. Relevant toolsets can cover repositories and code, issues and pull requests, Actions and workflows, and other service surfaces. Teams can enable toolsets selectively. API actions remain separate from local Git commands, so a remote change does not automatically mean the same change occurred in the working tree.
Configure Repository Scope and Guarded Write Permissions
The Claude plugin configuration references GITHUB_PERSONAL_ACCESS_TOKEN as a bearer token. Create or select a token with the smallest repository and operation scope needed for the task. Respect organization policies, branch protection, repository rules, and approval requirements.
For investigation, prefer read access. The local MCP server supports a read-only mode that suppresses write tools; a remote configuration should likewise be constrained through token scopes and selected toolsets. Keep the token out of prompts, source files, terminal history, and saved artifacts.
Before enabling writes, list the exact repositories and action types in scope: issue comments, branch operations, pull-request changes, release actions, or workflow control should never be bundled under a vague management instruction.
From Code Review and Branch Context to Accountable Delivery
Consider an issue linked to a failing pull request. First retrieve the issue's acceptance criteria, the pull-request diff, review comments, and the relevant Actions result. Claude Code can map those inputs to a repair plan and inspect the local code that owns the behavior.
After implementation and fresh tests, the agent can draft a pull-request update that explains the change, evidence, and residual risk. The developer reviews the local diff and the outbound text before any remote write occurs. If the issue state or assignee should change, handle that as a separate approved action.
This loop connects planning, code, and review without converting remote metadata into unattended authority.
Review Pull Requests, Issues, Status Changes, and CI Actions
Repository mutations, branch changes, issue updates, pull-request actions, releases, and workflow operations can affect collaborators and production systems. Require explicit intent, least-privilege access, and a preview of the exact action.
Do not bypass branch protection or required reviews. Check repository identity and default branch before writing. An Actions status can inform a decision, but it does not replace local reproduction or a review of what the workflow actually tested. Avoid duplicate issues or comments by retrieving the current thread immediately before posting.
Bring Verified GitHub Work into a Verdent Delivery Loop
Verdent's GitHub integration can view pull requests, manage issues, and trigger Actions. The Claude Code plugin can prepare repository context, while Verdent can continue approved work through its own plan-build-verify workflow. Use the permission and approval record of the system performing each action.
Give Verdent a scoped repository task and acceptance checks. Its agents can work in isolated Git worktrees and return verified changes. The GitHub integration can then support a reviewed pull request or update the existing delivery record. Repository policy remains the final gate.
Frequently Asked Questions
How does the plugin authenticate in Claude Code?
The checked-in configuration uses a personal access token. Effective access depends on token scope, repository and organization permissions, selected toolsets, and policy.
Does the plugin enable every API action?
No. Capabilities are exposed through toolsets and individual tools, and the connected identity and policy further limit what is available.
Is an MCP operation the same as a local Git command?
No. API operations affect remote resources, while local Git commands act on the checkout and repository state on the machine.
Which actions should require explicit approval?
Approve repository, branch, issue, pull-request, release, and workflow mutations individually, with the exact target and effect visible before execution.
Continue This Workflow With Verdent
Move a scoped repository issue through isolated implementation and fresh verification before review.