What is the key difference between Document Parser and Extend?

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

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

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

Can I use both Document Parser and Extend 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

Document Parser vs Extend

In-depth architectural comparison of the Document Parser and Extend 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: 39/100 (Fair) | Auth: No auth required

Extend

Developer Tools · Local stdio

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

Verdict Summary: Choose Document Parser if you need specialized Developer Tools tools running via a local process. Choose Extend 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 Extend 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 Extend Details

Feature & Specification Comparison

Specification	Document Parser Developer Tools	E Extend Developer Tools
Summary	Parse and extract structured data from various document formats (PDF, Word, HTML).	Turn documents into structured data: parse, extract, classify, split, and fill PDF forms.
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.

Extend 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": [
        "@agenson-horrowitz/document-parser-mcp"
      ]
    }
  }
}

Extend Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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