Docweave MCP vs Valet

In-depth architectural comparison of the Docweave MCP and Valet 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.

Which MCP Server Should You Choose?

Choose Docweave MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Freemium).
• Primary tools included: generate_pdf, read_pdf.

Explore Docweave MCP Details

Choose Valet when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: OAuth 2.0 (Freemium).
• Primary tools included: Streamable HTTP MCP endpoint, Agent workspace creation and deployment, File and folder publishing.

Explore Valet Details

Feature & Specification Comparison

Specification	Docweave MCP docweave Developer Tools	Valet Developer Tools
Summary	Generate and read PDFs for AI agents: a generatepdf tool (HTML, a URL, or a template + JSON → PDF) and a readpdf tool (a PDF → text/markdown). Run locally with npx @docweave/mcp or use the hosted streamable-HTTP endpoint. Chromium-rendered, priced per document.	Get share links, publish and manage websites, artifacts and agents. No account needed.
Category & Scope	Developer Tools

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "docweave-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@docweave/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "valet": {
      "url": "https://api.valet.dev/mcp"
    }
  }
}

Related MCP Server Comparisons