GitHub MCP server
Find a repository, confirm its owner, and file an issue through Arc0 MCP. The current GitHub tools cover repository discovery and issue creation; they do not expose pull-request or merge operations. Connect through Arc0 to use the actions your identity is allowed to call.
Working with GitHub
Turn an implementation finding into a GitHub issue without guessing the destination. Start with github.get_profile to confirm the connected account. github.list_repositories returns a small repository list; use github.list_repositories_page when you need explicit page size and continuation. Keep the owner and repository name from those results instead of inferring them from a project nickname.
For discovery by query, github.search_repositories delegates to GitHub’s remote MCP service. github.get_public_repository reads metadata for a named public repository through the public access path. These are useful for checking which project owns a dependency or where a reported problem should be filed.
Once the repository is settled, prepare a title and a body containing the observed behavior, reproduction steps, and expected result. github.create_issue submits those two fields and returns the issue number and URL. It does not assign labels, open a pull request, or merge code. If creation times out, inspect the repository’s issues in GitHub before submitting another copy.
Official MCP reference: GitHub documentation.
Agent workflows for GitHub.
Find the right repository
Use github.search_repositories to locate a repository before choosing where new work belongs.
Inventory accessible repositories
Use github.list_repositories_page and its continuation to review repositories visible to the connected user.
Check public project metadata
Use github.get_public_repository with an owner and repository name to inspect a public project.
File a scoped issue
Use github.create_issue to submit a reviewed title and body to a specific repository.
6 GitHub actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
5Look things up, subject to your permissions.
- github.search_repositoriesSearch repositories
Use when you need to find GitHub repositories matching a search query, with page and result-size controls.
- github.get_profileGet profile
Use when you need the connected GitHub account’s profile, including its user ID and login.
- github.list_repositoriesList repositories
Use when you need the first 20 repositories accessible to the connected GitHub account.
- github.list_repositories_pageList repositories by page
Use when you need a specific page of repositories accessible to the connected GitHub account, with a validated next-page number.
- github.get_public_repositoryGet public repository
Use when you need metadata for a public GitHub repository identified by its owner and repository name, without a connection.
write
1Create and change things. Allow, or ask the user first.
- github.create_issueCreate issue
Use when you need to open an issue with a title and optional body in a specified GitHub repository.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Control access to GitHub.
Connect the intended GitHub account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- github.create_issue: require approval
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How GitHub connects.
Connect GitHub using OAuth or API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- OAuth · API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use GitHub with your AI client.
Sign in to Arc0 and connect GitHub in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
GitHub with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingGitHub with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingGitHub with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingGitHub with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingGitHub with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingGitHub with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
More developer tools apps.
GitHub and Arc0, answered.
Is there an official GitHub MCP server, and how does Arc0 differ?
Yes. GitHub publishes an official MCP server. Arc0 uses it for repository search and REST calls for the other tools listed here, making those actions accessible alongside your other connected apps.
Which permissions does Arc0 need for GitHub?
OAuth requests read:user and repo; repo is broad repository access, not a read-only grant. A personal access token is also supported, subject to its permissions and repository access. The public-repository action can use public access.
Does this work with Claude, ChatGPT, Codex and Cursor?
Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. Repository permissions and Arc0 policies still apply.
How are credentials stored, refreshed and revoked?
Credentials are encrypted in Arc0’s vault. Arc0 stores the OAuth token or personal access token. It supports refresh when GitHub issues expiring tokens. OAuth disconnect attempts per-token revocation; revoke a personal token in GitHub settings to invalidate it at the source. Remote cleanup failure must not be treated as proof of provider-side revocation.
What happens with rate limits or errors?
GitHub applies primary and secondary rate limits. Arc0 reports rate-limit and permission failures rather than treating them as empty repository results. After an uncertain issue creation, check GitHub before retrying.
What is the availability of these GitHub tools?
GitHub is marked generally available in Arc0’s registry. Access to a particular repository or operation still depends on your connection and policies.
Plug GitHub into your agent.
GitHub MCP server: 6 actions including search repositories, get profile, list repositories. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
GitHub and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by GitHub.