Github MCP Server vs Relayer
A side-by-side look at the Github MCP Server and Relayer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
RelayerVersion ControlConversationally set up & manage an XNS Relayer over stdio: install, claim, VPD, S3, backups.39FairAuth: not declaredVerdict: choose Github MCP Server for version control work over a hosted endpoint; choose Relayer for version control. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Github MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GITHUB_OAUTH_CALLBACK_PORT. - You want tools like
get_file_contents, getFileContents.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R Relayer | |
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 81/100 · Excellent | 39/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Free |
| Required env vars | GITHUB_OAUTH_CALLBACK_PORT | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 33,518 | — |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Github MCP Server | View Relayer |
Tools & capabilities
Github MCP Server tools 2
get_file_contentsgetFileContents
Relayer tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Github MCP Server
{
"mcpServers": {
"github-github-mcp-server": {
"url": "https://api.githubcopilot.com/mcp/"
}
}
}
Relayer
No confirmed install command for Relayer yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Github MCP Server is categorized under Version Control and uses a remote HTTP/SSE transport. Relayer belongs to Version Control and uses an install path we have not confirmed yet. Pick Github MCP Server for version control work and Relayer for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Relayer has no confirmed install command yet — follow its own setup instructions.
Github MCP Server is listed as free. Auth: oauth 2.0. Relayer is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add github-github-mcp-server and relayer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Github MCP Server has a quality signal of 81/100 (Excellent) with 6 views, 0 installs and 33,518 GitHub stars. Relayer has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.