Magic MCP vs Domus
A side-by-side look at the Magic MCP and Domus MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
D
DomusHome Automation · Remote HTTP/SSEHomeowner's AI: view & update appliances, warranties, documents & maintenance for your home.39FairAuth: oauth 2.0Verdict: choose Magic MCP for architecture & design work as a local process; choose Domus for home automation over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
DChoose Domus when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | D Domus | |
|---|---|---|
| Category | Architecture & Design | Home Automation |
| Quality signal | 53/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | OAuth 2.0 |
| Pricing | Paid service | Not declared |
| Required env vars | TWENTY_FIRST_API_KEYAPI_KEY_21ST | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6,227 | — |
| Directory activity | 16 views 1 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Magic MCP | View Domus |
Tools & capabilities
Magic MCP tools
No tool names declared yet. Check the project README from the listing page.
Domus 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": {
"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"
}
}
}
}
Domus
{
"mcpServers": {
"domus": {
"command": "npx",
"args": [
"-y",
"domus"
]
}
}
}
Frequently asked questions
Magic MCP is categorized under Architecture & Design and uses a local stdio subprocess. Domus belongs to Home Automation and uses a remote HTTP/SSE transport. Pick Magic MCP for architecture & design work and Domus for home automation.
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.
Magic MCP is listed as a paid service. Auth: api key required. Domus has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 domus 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,227 GitHub stars. Domus has 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.