What is the key difference between Docfork MCP and Enclave402?

Docfork MCP belongs to the Version Control category with local stdio execution, while Enclave402 belongs to the Version Control category with local stdio execution.

How do I install Docfork MCP or Enclave402 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 Docfork MCP and Enclave402 free or paid?

Docfork MCP operates under a Free / Open Source model (No auth required). Enclave402 operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Docfork MCP lists 0 tools with 1 views and 488 GitHub stars. Enclave402 lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Docfork MCP and Enclave402 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

Docfork MCP vs Enclave402

In-depth architectural comparison of the Docfork MCP and Enclave402 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

Docfork MCP

Version Control · Local stdio

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

Enclave402

Version Control · Local stdio

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

Verdict Summary: Choose Docfork MCP if you need specialized Version Control tools running via a local process. Choose Enclave402 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 Docfork MCP 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 Docfork MCP Details

Choose Enclave402 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 Enclave402 Details

Feature & Specification Comparison

Specification	Docfork MCP Version Control	E Enclave402 Version Control
Summary	Up-to-date docs for AI agents. DEPRECATED: Use io.github.docfork/docfork instead.	x402 paid tools for agents: Polymarket signals, EIP-712 attestations. USDC on Base.
Category & Scope	Version Control	Version Control
Quality signal

Tools & Capabilities Breakdown

Docfork MCP Tools (0)

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

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

Docfork MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "docfork-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "dgrep"
      ]
    }
  }
}

Enclave402 Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Docfork MCP More alternatives to Enclave402 Version Control category hub