MCP Free Usdc Transfer MCP Server

1. Add this to your claude_desktop_config.json: ```json { "mcpServers": { "free-usdc-transfer": { "command": "npx", "args": [ "-y", "@magnetai/free-usdc-transfer" ], "env": { "COINBASE_CDP_API_KEY_NAME": "YOUR_COINBASE_CDP_API_KEY_NAME". That is what the mcp free usdc transfer mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

• Free USDC Transfers: Send USDC to any address or ENS/BaseName domain on Base - no fees, just simple transfers
• Coinbase MPC Wallet: Create and manage your Coinbase MPC wallet for secure, feeless transactions
• Name Resolution: Automatic support for ENS and BaseName domains

The tools it exposes

The server publishes 1 tool. What each one is for:

• create_coinbase_mpc_wallet — The create_coinbase_mpc_wallet tool exposed by this server

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: COINBASE_CDP_API_KEY_NAME, COINBASE_CDP_PRIVATE_KEY, YOUR_COINBASE_CDP_PRIVATE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Free Usdc Transfer's toolset — create_coinbase_mpc_wallet — is a fair guide to whether it matches your workflow. It is maintained by magnetai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.