What is the key difference between Dockhold and Quellgeist Commits?

Dockhold belongs to the Version Control category with cloud HTTP/SSE execution, while Quellgeist Commits belongs to the Version Control category with local stdio execution.

How do I install Dockhold or Quellgeist Commits 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 Dockhold and Quellgeist Commits free or paid?

Dockhold operates under a Free / Open Source model (No auth required). Quellgeist Commits operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Dockhold lists 0 tools with 0 views and 0 GitHub stars. Quellgeist Commits lists 0 tools with 1 views and 0 GitHub stars.

Can I use both Dockhold and Quellgeist Commits 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.

How do I install Dockhold or Quellgeist Commits in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Dockhold and Quellgeist Commits free to use, or do they require API keys?

Dockhold is listed under a Free / Open Source model with No auth required . Quellgeist Commits operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Dockhold and Quellgeist Commits at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both dockhold and quellgeist-commits as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Dockhold has a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars. Quellgeist Commits holds a Quality Score of 27 /100 ( Emerging ) with 1 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Dockhold vs Quellgeist Commits

In-depth architectural comparison of the Dockhold and Quellgeist Commits 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

Dockhold

Version Control · Remote HTTP/SSE

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

Quellgeist Commits

Version Control · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Dockhold if you need specialized Version Control tools running via a hosted cloud SSE transport. Choose Quellgeist Commits 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 Dockhold when:

You need dedicated capabilities in the Version Control domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Dockhold Details

Choose Quellgeist Commits 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).

Explore Quellgeist Commits Details

Feature & Specification Comparison

Specification	D Dockhold Version Control	Q Quellgeist Commits Version Control
Summary	Deploy a GitHub repo to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.	Read-only MCP server: get_recent_commits over a local deploy log (Quellgeist triage).
Category & Scope	Version Control	Version Control
Quality signal

Tools & Capabilities Breakdown

Dockhold Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Quellgeist Commits Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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).

Dockhold Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "dockhold": {
      "url": "https://dockhold.eu"
    }
  }
}

Quellgeist Commits Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "quellgeist-commits": {
      "command": "npx",
      "args": [
        "-y",
        "quellgeist-commits"
      ]
    }
  }
}

Frequently Asked Questions

Dockhold is categorized under Version Control and uses a remote streaming HTTP/SSE transport. In contrast, Quellgeist Commits belongs to Version Control using local stdio subprocess. Select Dockhold when you need capabilities focused on version control and Quellgeist Commits when you require tools for version control.

More alternatives to Dockhold More alternatives to Quellgeist Commits Version Control category hub

Related MCP Server Comparisons

Popular comparisons with Dockhold

Popular comparisons with Quellgeist Commits

M
Quellgeist Commits vs Mcp