Magic MCP vs Attestwire
A side-by-side look at the Magic MCP and Attestwire MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
AttestwireDeveloper Tools · Remote HTTP/SSEEN 16931: validate invoice data or a UBL/CII file, emit UBL or CII XML. XRechnung, Peppol. Not PDF.42FairAuth: not declaredVerdict: choose Magic MCP for developer tools work as a local process; choose Attestwire for developer tools 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 Developer Tools 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.
AChoose Attestwire when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Attestwire | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 42/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | TWENTY_FIRST_API_KEYAPI_KEY_21ST | None listed |
Tools & capabilities
Magic MCP tools
No tool names declared yet. Check the project README from the listing page.
Attestwire 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"
}
}
}
}
Attestwire
{
"mcpServers": {
"attestwire": {
"url": "https://api.attestwire.com/docs#mcp"
}
}
}
Frequently asked questions
Magic MCP is categorized under Developer Tools and uses a local stdio subprocess. Attestwire belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Magic MCP for developer tools work and Attestwire for developer tools.
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. Attestwire has no declared pricing — check the project's own site. 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 attestwire 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 5,997 GitHub stars. Attestwire has 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.