Workflowy vs Tampermonkey MCP

In-depth architectural comparison of the Workflowy and Tampermonkey MCP 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 Workflowy 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 Workflowy Details

Choose Tampermonkey MCP 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).
• Primary tools included: tampermonkey_get_connection_code, tampermonkey_list, tampermonkey_get.

Explore Tampermonkey MCP Details

Feature & Specification Comparison

Specification	Workflowy Developer Tools	Tampermonkey MCP Developer Tools
Summary	Create, update, complete nodes, search & replace with regex and dry run, usage reports, transforms	MCP server to manage your Tampermonkey scripts
Category & Scope	Developer Tools	Developer Tools
Quality signal

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": {
    "workflowy": {
      "command": "npx",
      "args": [
        "-y",
        "workflowy"
      ]
    }
  }
}

{
  "mcpServers": {
    "tampermonkey-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tampermonkey-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons