What is the key difference between Docfork Mcp and Image Processing?

Docfork Mcp belongs to the Version Control category with local stdio execution, while Image Processing belongs to the Version Control category with cloud HTTP/SSE execution.

How do I install Docfork Mcp or Image Processing 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 Image Processing free or paid?

Docfork Mcp operates under a Free / Open Source model (No auth required). Image Processing 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 0 views and 0 GitHub stars. Image Processing lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Docfork Mcp and Image Processing 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 Docfork Mcp or Image Processing 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 Docfork Mcp and Image Processing free to use, or do they require API keys?

Docfork Mcp is listed under a Free / Open Source model with No auth required . Image Processing 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 Docfork Mcp and Image Processing at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both docfork-mcp-2 and image-processing 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, Docfork Mcp has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Image Processing holds a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Docfork Mcp vs Image Processing

In-depth architectural comparison of the Docfork Mcp and Image Processing 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: 27/100 (Emerging) | Auth: No auth required

Image Processing

Version Control · Remote HTTP/SSE

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

Verdict Summary: Choose Docfork Mcp if you need specialized Version Control tools running via a local process. Choose Image Processing if your workspace requires Version Control integration with remote web transport. 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 Image Processing 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 Image Processing Details

Feature & Specification Comparison

Specification	D Docfork Mcp Version Control	I Image Processing Version Control
Summary	Up-to-date docs for AI agents. DEPRECATED: Use io.github.docfork/docfork instead.	Image processing for AI agents. Resize, convert, compress, and pipeline images.
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.

Image Processing 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",
        "docfork-mcp-2"
      ]
    }
  }
}

Image Processing Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "image-processing": {
      "url": "https://gitlab.com/pictomancer.ai/pig-gateway"
    }
  }
}

Frequently Asked Questions

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

More alternatives to Docfork Mcp More alternatives to Image Processing Version Control category hub