Oss Autopilot vs MCP Oss Onramp
A side-by-side look at the Oss Autopilot and MCP Oss Onramp 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 MCP Oss Onramp 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.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
GITHUB_TOKEN.
Choose MCP Oss Onramp when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 60/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | GITHUB_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 23 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Oss Autopilot | View MCP Oss Onramp |
Tools & capabilities
Oss Autopilot tools
No tool names declared yet. Check the project README from the listing page.
MCP Oss Onramp 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
{
"mcpServers": {
"costajohnt-oss-autopilot": {
"command": "npx",
"args": [
"@oss-autopilot/mcp@latest"
],
"env": {
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE"
}
}
}
}
MCP Oss Onramp
{
"mcpServers": {
"mcp-oss-onramp": {
"command": "npx",
"args": [
"-y",
"mcp-oss-onramp"
]
}
}
}
Frequently asked questions
Oss Autopilot is categorized under Version Control and uses a local stdio subprocess. MCP Oss Onramp belongs to Version Control and uses a local stdio subprocess. Pick Oss Autopilot for version control work and MCP Oss Onramp 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. MCP Oss Onramp has no declared pricing — check the project's own site. 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 mcp-oss-onramp 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 23 GitHub stars. MCP Oss Onramp has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.