What is the key difference between MCP Server Github Actions and MCP Git Ingest?

MCP Server Github Actions belongs to the Version Control category with local stdio execution, while MCP Git Ingest belongs to the Version Control category with local stdio execution.

How do I install MCP Server Github Actions or MCP Git Ingest in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Server Github Actions and MCP Git Ingest free or paid?

MCP Server Github Actions operates under a BYOK (Pay Provider Direct) model (API Key required). MCP Git Ingest operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

MCP Server Github Actions lists 9 tools with 2 views and 4 GitHub stars. MCP Git Ingest lists 6 tools with 5 views and 314 GitHub stars.

Can I use both MCP Server Github Actions and MCP Git Ingest together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Server Github Actions vs MCP Git Ingest

In-depth architectural comparison of the MCP Server Github Actions and MCP Git Ingest MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

MCP Server Github Actions

Version Control · Local stdio

Quality: 61/100 (Good) | Auth: API Key required

MCP Git Ingest

Version Control · Local stdio

Quality: 41/100 (Fair) | Auth: No auth required

Verdict Summary: Choose MCP Server Github Actions if you need specialized Version Control tools running via a local process. Choose MCP Git Ingest if your workspace requires Version Control integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCP Server Github Actions when:

You need dedicated capabilities in the Version Control domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: GITHUB_TOKEN.
Primary tools included: list_workflows, list_runs, get_run.

Explore MCP Server Github Actions Details

Choose MCP Git Ingest when:

You need dedicated capabilities in the Version Control domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Generate a GitHub repository directory tree, Read explicitly selected repository files, Skip .git directories in tree output.

Feature & Specification Comparison

Specification	MCP Server Github Actions ofershap Version Control	MCP Git Ingest adhikasp Version Control
Summary	GitHub Actions — view workflow runs, read logs, re-run failed jobs, and manage CI/CD.	Read and analyze GitHub repositories with your LLM
Category & Scope	Version Control

Tools & Capabilities Breakdown

MCP Server Github Actions Tools (9)

list_workflows

List all workflow files in a GitHub repository.

list_runs

List workflow runs for a repository. Optionally filter by workflow or status.

get_run

Get details of a specific workflow run.

get_run_logs

Get logs URL for a workflow run. GitHub returns a redirect to a zip file.

rerun_workflow

Re-run a complete workflow run.

rerun_failed_jobs

Re-run only the failed jobs from a workflow run.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCP Server Github Actions Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ofershap-mcp-server-github-actions": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-github-actions"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE"
      }
    }
  }
}

MCP Git Ingest Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "adhikasp-mcp-git-ingest": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/adhikasp/mcp-git-ingest",
        "mcp-git-ingest"
      ]
    }
  }
}

Frequently Asked Questions

MCP Server Github Actions is categorized under Version Control and uses a local stdio subprocess. In contrast, MCP Git Ingest belongs to Version Control using local stdio subprocess. Select MCP Server Github Actions when you need capabilities focused on version control and MCP Git Ingest when you require tools for version control.

More alternatives to MCP Server Github Actions More alternatives to MCP Git Ingest Version Control category hub Canonical compare URL