runelay+GitHubIntegration · OAuth login
GitHub on Runelay, an open source MCP gateway
GitHub's official MCP server, behind your own Runelay endpoint. Log in once with OAuth and every agent can read repositories, work on issues and handle pull requests with your GitHub permissions.
GitHub's own MCP server, shared by every agent
The catalog entry points at api.githubcopilot.com/mcp/, the remote MCP server GitHub maintains. Runelay does not wrap or rewrite its tools; it holds the token and forwards the calls.
GitHub groups the server's tools into toolsets. Its documented default set is context, repos, issues, pull requests and users, which covers the day-to-day work below.
What your agent can do on GitHub
- Repositories and code. Read files with
get_file_contents, search withsearch_codeandsearch_repositories, inspect history withlist_commitsandget_commit, and write withcreate_branch,create_or_update_fileandpush_files. - Issues. Find them with
list_issuesandsearch_issues, read one withissue_read, open or edit withissue_writeand manage sub-issues withsub_issue_write. - Pull requests. List, search and read pull requests, open them with
create_pull_request, update them, leave a review withpull_request_review_writeand merge withmerge_pull_request. - Context.
get_metells the agent who it is acting as, andsearch_usersfinds people by name.
Try asking
- “Summarize the open pull requests in my repo and say which ones are waiting on me.”
- “Find where the rate limiter is defined in this repository and explain it.”
- “Open an issue for the failing login redirect with the steps I just described.”
How it signs in
- OAuth through the Runelay broker. You approve a GitHub OAuth app; no client of your own to register.
- Scopes requested:
repoandread:user. The agent can reach the repositories your GitHub account can reach, private ones included. - Prefer a token? Paste a GitHub personal access token instead, and its permissions set the limit.
What this connection does
Repositories, issues and pull requests. Runelay connects to the GitHub remote MCP server at https://api.githubcopilot.com/mcp/ and puts its tools behind your own endpoint.
Agents find them with search_tools and run them with call_tool, so the GitHub tool list is not loaded into context until it is needed.
Connect GitHub
Open the connectors in the panel
Pick GitHub from the catalog.
Log in once
A browser tab opens on GitHub. Approve the access and close it.
Done
The token is stored encrypted on your server and refreshed by Runelay. Every agent with a Runelay key can use the connection.
Use GitHub in your agents
Agents do not need a GitHub entry of their own. Point each one at Runelay and GitHub is there.
Questions
Can the agent push code or merge pull requests?
Yes. The default toolsets include push_files, create_or_update_file and merge_pull_request, so the agent can write wherever your account can. If that is too much, connect with a fine-grained personal access token limited to the repositories and permissions you choose.
Does it see my private repositories?
With OAuth it does: the repo scope covers private repositories your account can reach. A fine-grained token narrows that to the repositories you select.
Is this the same server Copilot uses?
It is the remote GitHub MCP server at api.githubcopilot.com/mcp/, maintained by GitHub. Runelay connects to it from your server and keeps the token there.