Epinu vs Magic MCP
A side-by-side look at the Epinu and Magic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Epinu for developer tools work over a hosted endpoint; choose Magic MCP 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?
Choose Epinu when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
projects_search, getting_started, marketplace_listings_search.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Architecture & Design |
| Quality signal | 55/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | TWENTY_FIRST_API_KEYAPI_KEY_21ST |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6,209 |
| Directory activity | 1 views 0 installs 0 upvotes | 16 views 1 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Epinu | View Magic MCP |
Tools & capabilities
Epinu tools 5
projects_searchSearch Epinu real-asset projects. Returns bounded summaries only; call projects_get_deep_dive for detailed packets. Results include public projects plus the token owner's own archived, draft, or unpublished projects for duplicate checks; another owner's unpublished projects are never returned. Available without a token for public results only.getting_startedStart here: platform overview, the proposal/approval operating model, auth rules, common flows, and agent etiquette. Static content — requires no scopes.marketplace_listings_searchSearch the Epinu marketplace for equipment, services, and assets. Returns summaries only; call marketplace_listing_get for detailed packets.searchUnified read-only search across public Epinu projects and marketplace listings. Returns { id, title, url } results; call fetch with a returned id for the full document. Available without a token; public data only. Additive alias over projects_search and marketplace_listings_search.fetchFetch the full document for one search result by its opaque id (project:<uuid> or listing:<uuid>). Returns { id, title, text, url, metadata }. Available without a token; public data only. Wraps projects_get_deep_dive and marketplace_listing_get. Unknown or malformed ids return a clean not-found.
Magic MCP 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.
Epinu
{
"mcpServers": {
"epinu-2": {
"url": "https://api.epinu.ai/api/agent/mcp"
}
}
}
Magic MCP
{
"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"
}
}
}
}
Frequently asked questions
Epinu is categorized under Developer Tools and uses a remote HTTP/SSE transport. Magic MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Epinu for developer tools work and Magic MCP 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.
Epinu has no declared pricing — check the project's own site. Magic MCP is listed as a paid service. Auth: api key required. 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 epinu-2 and 21st-dev-magic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Epinu has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Magic MCP has 53/100 (Good) with 16 views, 1 installs and 6,209 GitHub stars.