Oss Autopilot vs Gha Intel
A side-by-side look at the Oss Autopilot and Gha Intel 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 Gha Intel 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 Gha Intel when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GITHUB_TOKEN. - You want tools like
list_workflow_performance, analyze_workflow_config, get_billing_usage.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 60/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | GITHUB_TOKEN | GITHUB_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 23 | 2 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Oss Autopilot | View Gha Intel |
Tools & capabilities
Oss Autopilot tools
No tool names declared yet. Check the project README from the listing page.
Gha Intel tools 3
list_workflow_performanceFetch the last N workflow runs and compute job-level timing statistics (avg, min, max, p95) across those runs. Useful for identifying slow jobs and trends.analyze_workflow_configParse a GitHub Actions workflow YAML (provided as a string) and identify optimization opportunities: missing caches, matrix strategy, concurrency controls, slow dependency installs, artifact handling, and more.get_billing_usageRetrieve GitHub Actions billing and cache usage statistics for an owner (user or org), optionally scoped to a specific repository.
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"
}
}
}
}
Gha Intel
{
"mcpServers": {
"gha-intel": {
"command": "npx",
"args": [
"-y",
"@barissozudogru/gha-intel-mcp"
],
"env": {
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Oss Autopilot is categorized under Version Control and uses a local stdio subprocess. Gha Intel belongs to Version Control and uses a local stdio subprocess. Pick Oss Autopilot for version control work and Gha Intel 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. Gha Intel 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 gha-intel 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. Gha Intel has 60/100 (Good) with 1 views, 0 installs and 2 GitHub stars.