Webclaw vs Yuque MCP Server

In-depth architectural comparison of the Webclaw and Yuque MCP Server 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 Webclaw when:

• You need dedicated capabilities in the Other Tools and Integrations domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: scrape, crawl, map.

Explore Webclaw Details

Choose Yuque MCP Server when:

• You need dedicated capabilities in the Other Tools and Integrations domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: YUQUE_API_TOKEN, YUQUE_API_BASE_URL, PORT.
• Primary tools included: Yuque document CRUD operations, Knowledge-base and document listing, Content search with filters.

Feature & Specification Comparison

Specification	Webclaw 0xMassi Other Tools and Integrations	Yuque MCP Server HenryHaoson Other Tools and Integrations
Summary
Category & Scope	Other Tools and Integrations	Other Tools and Integrations

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": {
    "0xmassi-webclaw": {
      "command": "npx",
      "args": [
        "-y",
        "create-webclaw"
      ]
    }
  }
}

{
  "mcpServers": {
    "henryhaoson-yuque-mcp-server": {
      "url": "http://localhost:3000/sse?accessToken=your_token_here&baseUrl=https://custom.yuque.api/v2"
    }
  }
}

Related MCP Server Comparisons