A side-by-side look at the Oss Autopilot and GitHub (read Only) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Oss Autopilot for version control work as a local process; choose GitHub (read Only) for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Oss Autopilot when
You need dedicated capabilities in the Version Control domain.
No tool names declared yet. Check the project README from the listing page.
GitHub (read Only) 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.
Oss Autopilot is categorized under Version Control and uses a local stdio subprocess. GitHub (read Only) belongs to Version Control and uses a local stdio subprocess. Pick Oss Autopilot for version control work and GitHub (read Only) 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.
Oss Autopilot is listed as free. Auth: other. GitHub (read Only) has no declared pricing — check the project's own site. Auth: api key required. 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 costajohnt-oss-autopilot and github-read-only as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Oss Autopilot has a quality signal of 60/100 (Good) with 6 views, 0 installs and 17 GitHub stars. GitHub (read Only) has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.