Wovo vs Floom

In-depth architectural comparison of the Wovo and Floom 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 Wovo 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 Wovo Details

Choose Floom 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 Floom Details

Feature & Specification Comparison

Specification	Wovo Developer Tools	Floom Developer Tools
Summary	Deploy HTML from any AI tool to a versioned, shareable library on wovo.dev; manage pages.	Deploy Python functions as web apps with auto-generated UI, REST API, and shareable links.
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": {
    "wovo": {
      "command": "npx",
      "args": [
        "-y",
        "@gowovo/wovo"
      ]
    }
  }
}

{
  "mcpServers": {
    "floom": {
      "command": "npx",
      "args": [
        "-y",
        "@floomhq/floom"
      ]
    }
  }
}

Related MCP Server Comparisons