Flato Design MCP vs StyleKit

A side-by-side look at the Flato Design MCP and StyleKit MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Flato Design MCP logoFlato Design MCPArchitecture & Design · Remote HTTP/SSEConnect AI agents to Flato's editable canvas runtime through a hosted MCP server.37FairAuth: not declaredStyleKit logoStyleKitArchitecture & Design · Local subprocess (stdio)Search 148 curated design styles and pull tokens, recipes, and shadcn commands into your AI IDE.52GoodAuth: not declared

Verdict: choose Flato Design MCP for architecture & design work over a hosted endpoint; choose StyleKit for architecture & design as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Flato Design MCP logoChoose Flato Design MCP when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a remote HTTP/SSE transport.
Explore Flato Design MCP

StyleKit logoChoose StyleKit when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
Explore StyleKit

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFlato Design MCP logoFlato Design MCPStyleKit logoStyleKit
CategoryArchitecture & DesignArchitecture & Design
Quality signal37/100 · Fair52/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2630
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Flato Design MCP tools

No tool names declared yet. Check the project README from the listing page.

StyleKit tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Flato Design MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "flato-design-mcp": {
      "url": "https://api.flato.ai/api/mcp/editor"
    }
  }
}

StyleKit

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "stylekit": {
      "command": "npx",
      "args": [
        "-y",
        "shadcn"
      ]
    }
  }
}

Frequently asked questions

Flato Design MCP is categorized under Architecture & Design and uses a remote HTTP/SSE transport. StyleKit belongs to Architecture & Design and uses a local stdio subprocess. Pick Flato Design MCP for architecture & design work and StyleKit for architecture & design.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Flato Design MCP has no declared pricing — check the project's own site. StyleKit has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add flato-design-mcp and stylekit as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Flato Design MCP has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. StyleKit has 52/100 (Good) with 2 views, 0 installs and 630 GitHub stars.