What is the key difference between Magic MCP and Foundry IMS?

Magic MCP belongs to the Developer Tools category with local stdio execution, while Foundry IMS belongs to the Developer Tools category with cloud HTTP/SSE execution.

How do I install Magic MCP or Foundry IMS in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Magic MCP and Foundry IMS free or paid?

Magic MCP operates under a Paid Service model (API Key required). Foundry IMS operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Magic MCP lists 5 tools with 13 views and 5,635 GitHub stars. Foundry IMS lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Magic MCP and Foundry IMS together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Magic MCP or Foundry IMS in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Magic MCP and Foundry IMS free to use, or do they require API keys?

Magic MCP is listed under a Paid Service model with API Key required . Foundry IMS operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Magic MCP and Foundry IMS at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both 21st-dev-magic-mcp and foundry-ims as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Magic MCP has a Quality Score of 51 /100 ( Good ) with 13 views, 1 installs, and 5,635 GitHub stars. Foundry IMS holds a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Magic MCP vs Foundry IMS

In-depth architectural comparison of the Magic MCP and Foundry IMS 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.

At a Glance & Executive Verdict

Magic MCP

Developer Tools · Local stdio

Quality: 51/100 (Good) | Auth: API Key required

Foundry IMS

Developer Tools · Remote HTTP/SSE

Quality: 42/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Magic MCP if you need specialized Developer Tools tools running via a local process. Choose Foundry IMS if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Magic MCP when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Paid Service).
You have access to required keys: API_KEY, TWENTY_FIRST_API_KEY, API_KEY_21ST.
Primary tools included: Component generation and refinement, Component and theme catalog search, Logo search tool.

Explore Magic MCP Details

Choose Foundry IMS when:

You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Foundry IMS Details

Feature & Specification Comparison

Specification	Magic MCP 21st-dev Developer Tools	F Foundry IMS Developer Tools
Summary	Create crafted UI components inspired by the best 21st.dev design engineers.	Manage a Foundry IMS catalog: products, variants, inventory, brands, categories and BOMs.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Magic MCP Tools (5)

Component generation and refinement

Component and theme catalog search

Logo search tool

Bookmarks and team library management

Profile and API key management

Foundry IMS Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

Magic MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "21st-dev-magic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@21st-dev/cli@latest"
      ],
      "env": {
        "API_KEY": "YOUR_API_KEY_HERE",
        "TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
        "API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
      }
    }
  }
}

Foundry IMS Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "foundry-ims": {
      "url": "https://foundryims.com/integrations/ai/claude/"
    }
  }
}

Frequently Asked Questions

Magic MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Foundry IMS belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Magic MCP when you need capabilities focused on developer tools and Foundry IMS when you require tools for developer tools.

More alternatives to Magic MCP More alternatives to Foundry IMS Developer Tools category hub