What is the key difference between Document Parser and DocSlicer?

Document Parser belongs to the Developer Tools category with local stdio execution, while DocSlicer belongs to the Developer Tools category with local stdio execution.

How do I install Document Parser or DocSlicer 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 Document Parser and DocSlicer free or paid?

Document Parser operates under a Free / Open Source model (No auth required). DocSlicer operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Document Parser lists 0 tools with 0 views and 0 GitHub stars. DocSlicer lists 0 tools with 0 views and 14 GitHub stars.

Can I use both Document Parser and DocSlicer 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 Document Parser or DocSlicer 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 Document Parser and DocSlicer free to use, or do they require API keys?

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

Yes! MCP clients support multi-server orchestration. You can include both document-parser and docslicer 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, Document Parser has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. DocSlicer holds a Quality Score of 43 /100 ( Fair ) with 0 views, 0 installs, and 14 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Document Parser vs DocSlicer

In-depth architectural comparison of the Document Parser and DocSlicer 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

Document Parser

Developer Tools · Local stdio

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

DocSlicer

Developer Tools · Local stdio

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

Verdict Summary: Choose Document Parser if you need specialized Developer Tools tools running via a local process. Choose DocSlicer if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Document Parser when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Document Parser Details

Choose DocSlicer when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore DocSlicer Details

Feature & Specification Comparison

Specification	D Document Parser Developer Tools	D DocSlicer Developer Tools
Summary	Parse and extract structured data from various document formats (PDF, Word, HTML).	Deterministic hierarchical document parser and chunker for PDF, DOCX, PPTX and HTML.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Document Parser Tools (0)

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

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

Document Parser Configuration

mcpServers (Claude Desktop / Cursor)

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

DocSlicer Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "docslicer": {
      "command": "uvx",
      "args": [
        "--from"
      ]
    }
  }
}

Frequently Asked Questions

Document Parser is categorized under Developer Tools and uses a local stdio subprocess. In contrast, DocSlicer belongs to Developer Tools using local stdio subprocess. Select Document Parser when you need capabilities focused on developer tools and DocSlicer when you require tools for developer tools.

More alternatives to Document Parser More alternatives to DocSlicer Developer Tools category hub Canonical compare URL