NexusToken vs Magic MCP
A side-by-side look at the NexusToken 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 NexusToken for coding agents work as a local process; 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 NexusToken when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
NEXUS_BASE_URL.
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 | Coding Agents | Architecture & Design |
| Quality signal | 35/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Paid service |
| Required env vars | NEXUS_BASE_URL | TWENTY_FIRST_API_KEYAPI_KEY_21ST |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 6,217 |
| Directory activity | 0 views 0 installs 0 upvotes | 16 views 1 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View NexusToken | View Magic MCP |
Tools & capabilities
NexusToken tools
No tool names declared yet. Check the project README from the listing page.
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.
NexusToken
{
"mcpServers": {
"nexustoken": {
"command": "uvx",
"args": [
"nexustoken-sdk"
],
"env": {
"NEXUS_BASE_URL": "YOUR_NEXUS_BASE_URL_HERE"
}
}
}
}
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
NexusToken is categorized under Coding Agents and uses a local stdio subprocess. Magic MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick NexusToken for coding agents 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.
NexusToken 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 nexustoken and 21st-dev-magic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, NexusToken has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Magic MCP has 53/100 (Good) with 16 views, 1 installs and 6,217 GitHub stars.