In-depth architectural comparison of the Mcp and Mcp Ipfs MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Mcp
Cloud Platforms · Remote HTTP/SSE
Quality: 56/100 (Good) | Auth: API Key required
Mcp Ipfs
Cloud Platforms · Local stdio
Quality: 40/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Mcp if you need specialized Cloud Platforms tools running via a hosted cloud SSE transport. Choose Mcp Ipfs if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Mcp when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: AGENTMETAL_BASE_URL, WALLET_PRIVATE_KEY, AGENTMETAL_NETWORK, AGENTMETAL_MAX_USDC, AGENTMETAL_API_KEY.
Provision, SSH into, run commands on, and manage Linux VPSes from an agent — pay USDC over x402 or by card over HTTP 402, a running box in under 60s. No signup, no API key to buy.
List plans, locations, and add-on pricing (bandwidth, storage). The free discovery hook.
provision_server
Provision a VPS (`plan`, `days`, optional `ssh_key`/`via`, `managed_key`) → id, IPv4, SSH. With `managed_key:true`, a server-side keypair is generated, authorized, and the private key returned **once** (stored only encrypted) to enable `exec_command`.
get_server
Status, IPv4, expiry, bandwidth, storage for a server id
list_servers
Fleet for a wallet/account
extend_server
Extend a lease by N days
destroy_server
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Mcp is categorized under Cloud Platforms and uses a remote streaming HTTP/SSE transport. In contrast, Mcp Ipfs belongs to Cloud Platforms using local stdio subprocess. Select Mcp when you need capabilities focused on cloud platforms and Mcp Ipfs when you require tools for cloud platforms.
Hypervisor-level diagnostics without logging in: status, recent provider actions, a VNC console URL, and live CPU/disk/net metrics (no text boot log exists provider-side)
exec_command
Run a shell command as **root** over SSH → exit_code/stdout/stderr. Requires a server provisioned with `managed_key:true`. Bounded: 1–120 s timeout, 256 KB output cap.
get_firewall
Read a box's edge-firewall rules. Callable from the box itself (source-IP identity) or with an account key.
manage_firewall
Open/close inbound ports on a box's edge firewall (protocol/port/source_ips). From the box itself or with an account key; SSH-lockout guarded.
claim_account
Email a one-time claim code (via AWS SES)
+1 more tools listed on main page
Mcp Ipfs Tools (5)
Wraps w3 CLI commands for storacha.network integration
Supports authentication and agent management
Manages spaces, data uploads, and deletions
Handles delegations, proofs, and key/token management
Provides account billing and usage reporting tools