Give your AI agent safe access to GitHub
Your agent can push commits, open PRs, and manage branches. Approved actions issue a short-lived token scoped to exactly what's needed — nothing more, nothing lingering.
Step 1
Connect your GitHub account
Open the AgentBlocks dashboard, click “Connect GitHub,” and authenticate. That's the entire setup. Your agent now has access to your repositories — but only within the rules you're about to set. You can disconnect at any time.
Superpowers
Jane Smith
jane@example.com
GitHub
Push commits, open PRs, and manage repositories
GitHub not yet connected
Connect a GitHub account to give your agent access to your repositories.
Step 2
Set your GitHub rules
Choose exactly what your agent can do on its own — browsing repos, reading commits, viewing PRs — and what needs your say-so. Require approval before it pushes code or opens PRs. Block anything you don't want it to touch at all. You control every action, on every repo.
Repository
Commits
Reading commit history is safe. Pushing code changes your repo permanently.
List commits
Browse commit history and diffs.
Push commits
Write code changes to a branch.
Pull Requests
Reading is safe. Opening and merging PRs changes your codebase.
List & view PRs
See open pull requests and read their diffs.
Open a PR
Create a new pull request from a branch.
Merge a PR
Merge a pull request into the target branch.
Issues
Reading issues is safe. Creating them writes to your repo.
List & read issues
Browse open and closed issues.
Create an issue
Open a new issue on a repository.
Step 3
Connect your agent
Open Claude Code or your terminal-based AI agent and add AgentBlocks as an MCP server. One command. Your agent instantly knows it has GitHub access and exactly what it's allowed to do.
$ claude mcp add agentblocks
https://mcp.agentblocks.ai/v1
--api-key sk-ab-••••••••
✓ MCP server "agentblocks" added
✓ GitHub access ready — 1 repo connected (acme/backend)
Push requires approval · reads are auto-allowed
Step 4
Give it a task
Ask your agent to work on your codebase and it gets started. It browses the repo, reads the right files, makes edits — all the read and write operations that you've set to auto-allow happen without interruption. When it hits something that needs a push or PR, it stops and asks.
Step 5
Approve write actions
When your agent is ready to push code or open a pull request, it shows you exactly what it wants to do — the repo, the branch, the files changed, the commit message — before anything is pushed. One tap to approve, and it's done.
AgentBlocks
WhatsApp approval
Your agent wants to push code to your GitHub repository.
Repo: acme/backend
Branch: fix/auth-jwt
1 commit · 1 file changed
Refactor auth module to use JWT refresh tokens
+45 -23 src/auth/auth.ts
11:34
Short-lived, scoped credentials
Every approved action uses a token issued for that moment only. It can push to that one branch, in that one repo — nothing else. It expires in minutes. Once the action completes, it's gone. No credentials sitting around, no way for them to be reused or leaked.
You approve
One tap in WhatsApp, Slack, or email
Scoped token issued
fix/auth-jwt only · expires in 5 mins
Action executes
Push runs with minimum permissions
Token destroyed
Access revoked immediately. Nothing lingers.
You approve
One tap in WhatsApp, Slack, or email
Scoped token issued
fix/auth-jwt only · expires in 5 mins
Action executes
Push runs with minimum permissions
Token destroyed
Access revoked immediately. Nothing lingers.
Step 6
Then let it run
Once you're happy with your rules, your agent works through your codebase on its own — reading files, making edits, building up context. It only asks when there's something to push or merge. You approve from wherever you are in seconds, and it keeps going.
7
This session
6
Auto-approved
1
Waiting for you
11:30
Listed repos
1 connected · acme/backend
11:31
Listed files in src/auth
4 files found
11:31
Read auth.ts
312 lines parsed
11:32
Read auth.utils.ts
89 lines parsed
11:32
Read auth.middleware.ts
61 lines parsed
11:33
Edited auth.ts
3 changes — JWT refresh token logic
11:34
Push to origin/fix/auth-jwt
acme/backend · 1 file · 3 changes
Explore other superpowers
Every integration works the same way — scoped access, approval controls, full audit trail.
Give your agent safe
GitHub access today.
One paste. One API key. Your agent handles the rest.
🦞 Works great with OpenClaw, Claude Cowork and Claude Code