Magic MCP vs Robomart

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

Magic MCP logoMagic MCPArchitecture & Design · Local subprocess (stdio)Create crafted UI components inspired by the best 21st.dev design engineers.53GoodAuth: api key required
R
RobomartDelivery
Driverless delivery.34EmergingAuth: not declared

Verdict: choose Magic MCP for architecture & design work as a local process; choose Robomart for delivery. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Magic MCP logoChoose Magic MCP when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: TWENTY_FIRST_API_KEY, API_KEY_21ST.
Explore Magic MCP

R
Choose Robomart when

  • You need dedicated capabilities in the Delivery domain.
Explore Robomart

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMagic MCP logoMagic MCP
R
Robomart
CategoryArchitecture & DesignDelivery
Quality signal53/100 · Good34/100 · Emerging
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthAPI key requiredNot declared
PricingPaid serviceNot declared
Required env varsTWENTY_FIRST_API_KEYAPI_KEY_21STNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars6,193—
Directory activity 16 views 1 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Magic MCP tools

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

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

Magic MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "21st-dev-magic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@21st-dev/cli@latest"
      ],
      "env": {
        "TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
        "API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
      }
    }
  }
}

Robomart

No confirmed install command for Robomart yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Magic MCP is categorized under Architecture & Design and uses a local stdio subprocess. Robomart belongs to Delivery and uses an install path we have not confirmed yet. Pick Magic MCP for architecture & design work and Robomart for delivery.

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. Robomart has no confirmed install command yet — follow its own setup instructions.

Magic MCP is listed as a paid service. Auth: api key required. Robomart 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 21st-dev-magic-mcp and robomart as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Magic MCP has a quality signal of 53/100 (Good) with 16 views, 1 installs and 6,193 GitHub stars. Robomart has 34/100 (Emerging) with 2 views, 0 installs and 0 GitHub stars.