Auxen vs Magic MCP
A side-by-side look at the Auxen 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 Auxen for conversational ai 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 Auxen when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
auxen_list_models, auxen_get_instance_status, auxen_list_instances.
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 | Conversational AI | Architecture & Design |
| Quality signal | 48/100 · Fair | 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,193 |
| Directory activity | 1 views 0 installs 0 upvotes | 16 views 1 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Auxen | View Magic MCP |
Tools & capabilities
Auxen tools 6
auxen_list_modelsread-onlyauxen_get_instance_statusread-onlyauxen_list_instancesread-onlyauxen_get_balanceread-onlyauxen_provision_modeldestructiveauxen_destroy_instancedestructive
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.
Auxen
{
"mcpServers": {
"auxen": {
"url": "https://api.auxen.ai/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
Auxen is categorized under Conversational AI and uses a remote HTTP/SSE transport. Magic MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Auxen for conversational ai 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.
Auxen 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 auxen and 21st-dev-magic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Auxen has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Magic MCP has 53/100 (Good) with 16 views, 1 installs and 6,193 GitHub stars.