CD MCP Server vs MCP Server Github Actions
A side-by-side look at the CD MCP Server and MCP Server Github Actions MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CD MCP Server for version control work as a local process; choose MCP Server Github Actions 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 CD MCP Server 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, GH_TOKEN. - You want tools like
github_get_authenticated_user, github_get_rate_limit, github_create_repository.
Choose MCP Server Github Actions when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GITHUB_TOKEN. - You want tools like
list_workflows, list_runs, get_run.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 60/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | GITHUB_TOKENGH_TOKEN | GITHUB_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 4 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 70 | 9 |
| Full listing | View CD MCP Server | View MCP Server Github Actions |
Tools & capabilities
CD MCP Server tools 70
github_get_authenticated_userGet the authenticated GitHub user (validates token and shows login).github_get_rate_limitCheck REST API rate limit status for the current token.github_create_repositoryCreate a new repository for the authenticated user or an organization.github_get_repositoryGet repository metadata.github_list_repositoriesList repositories for a user or organization.github_create_branchCreate a branch from an existing ref (e.g. main).github_fork_repositoryFork a repository to the authenticated user or an organization.github_list_commitsList commits on a branch or for the whole repo.github_get_commitGet a single commit with files changed.github_compare_commitsCompare two commits (base...head) — useful for release notes and PR scope.github_create_commitCreate a commit on a branch by updating one or more files (GitHub Git API — no local clone required).github_get_combined_statusGet combined commit status (legacy statuses + check runs summary) for CI/CD gates.- +58 more on the listing page
MCP Server Github Actions tools 9
list_workflowsList all workflow files in a GitHub repository.list_runsList workflow runs for a repository. Optionally filter by workflow or status.get_runGet details of a specific workflow run.get_run_logsGet logs URL for a workflow run. GitHub returns a redirect to a zip file.rerun_workflowRe-run a complete workflow run.rerun_failed_jobsRe-run only the failed jobs from a workflow run.cancel_runCancel a workflow run that is in progress or queued.list_artifactsList artifacts produced by a workflow run.trigger_workflowTrigger a workflow run via workflow_dispatch. Requires a workflow with workflow_dispatch enabled.
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.
CD MCP Server
{
"mcpServers": {
"github-ci-cd-mcp-server": {
"command": "npx",
"args": [
"-y",
"@kinus/github-cicd-mcp"
],
"env": {
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE",
"GH_TOKEN": "YOUR_GH_TOKEN_HERE"
}
}
}
}
MCP Server Github Actions
{
"mcpServers": {
"ofershap-mcp-server-github-actions": {
"command": "npx",
"args": [
"-y",
"mcp-server-github-actions"
],
"env": {
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE"
}
}
}
}
Frequently asked questions
CD MCP Server is categorized under Version Control and uses a local stdio subprocess. MCP Server Github Actions belongs to Version Control and uses a local stdio subprocess. Pick CD MCP Server for version control work and MCP Server Github Actions 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.
CD MCP Server has no declared pricing — check the project's own site. MCP Server Github Actions is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 github-ci-cd-mcp-server and ofershap-mcp-server-github-actions as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CD MCP Server has a quality signal of 60/100 (Good) with 2 views, 0 installs and 2 GitHub stars. MCP Server Github Actions has 63/100 (Good) with 5 views, 0 installs and 4 GitHub stars.