What is the key difference between Agentql and Document Parser?

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

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

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

Which MCP server has more tools and community activity?

Agentql lists 0 tools with 0 views and 30 GitHub stars. Document Parser lists 0 tools with 0 views and 0 GitHub stars.

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

Agentql vs Document Parser

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

Agentql

Developer Tools · Local stdio

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

Document Parser

Developer Tools · Local stdio

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

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

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

Feature & Specification Comparison

Specification	Agentql Developer Tools	Document Parser Developer Tools
Summary
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Agentql Tools (0)

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

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

Agentql Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "agentql": {
      "command": "uvx",
      "args": [
        "mcparmory-github"
      ]
    }
  }
}

Document Parser Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "document-parser": {
      "command": "npx",
      "args": [
        "@agenson-horrowitz/document-parser-mcp"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Agentql More alternatives to Document Parser Developer Tools category hub