MCP Server: Free USDC Transfers via Coinbase MPC

Overview

This MCP (Model Context Protocol) server implements feeless USDC transfers on Base by integrating Coinbase CDP MPC (multi-party computation) wallets. It lets applications and agents schedule USDC payouts that use Coinbase’s MPC signing to avoid on-chain gas costs for end users, while keeping signing keys secure and off the host machine.

The server exposes two high-level operations: create a Coinbase MPC wallet and schedule USDC transfers to an on-chain address, ENS, or BaseName. It resolves human-readable names, schedules transactions on Base, and returns transaction links for monitoring. Transactions are scheduled and returned immediately — the server does not block waiting for final chain confirmation.

Features

• Free USDC transfers on Base via Coinbase MPC wallet integration
• Create and manage Coinbase CDP MPC wallets programmatically
• ENS and BaseName resolution for human-friendly recipients
• Transaction scheduling (non-blocking) with BaseScan links for tracking
• Seed info saved locally for wallet recovery (developer-accessible file)
• Easy integration with Claude Desktop / MCP-compatible host agents

Installation / Configuration

Prerequisites:

• Node.js (LTS) and npm or npx
• Coinbase CDP account and API key (see Coinbase CDP docs)
• A host able to run an MCP server (Claude Desktop, Magnet Desktop, or your own MCP runtime)

Install or run via npx (example for a Claude Desktop MCP entry):

{
  "mcpServers": {
    "free-usdc-transfer": {
      "command": "npx",
      "args": [
        "-y",
        "@magnetai/free-usdc-transfer"
      ],
      "env": {
        "COINBASE_CDP_API_KEY_NAME": "YOUR_COINBASE_CDP_API_KEY_NAME",
        "COINBASE_CDP_PRIVATE_KEY": "YOUR_COINBASE_CDP_PRIVATE_KEY"
      }
    }
  }
}

Environment variables

How to get an API key:

1. Sign up for a Coinbase CDP account: https://portal.cdp.coinbase.com/
2. Create an API key from the developer dashboard and copy the key name and private key into the server env.

Local wallet seed storage

• The MPC wallet seed (metadata required by the integration) is saved to your Documents folder as mpc_info.json. On macOS/Linux this is typically $HOME/Documents/mpc_info.json; on Windows %USERPROFILE%\Documents\mpc_info.json. Protect this file — treat it like any sensitive key material.

Running via magnet-desktop

• The package can also be installed and run from Magnet Desktop (see the repository README and Magnet Desktop docs).

Repository

• Source and issues: https://github.com/magnetai/mcp-free-usdc-transfer

Available Tools / Resources

Functions exposed by the MCP server

1. transfer-usdc

• Description: Schedule a USDC transfer on Base to an address or ENS/BaseName domain. The server resolves names, constructs and signs the transaction using Coinbase MPC, and schedules it for submission. Because chain timing is uncertain, the function schedules and returns immediately; it does not wait for confirmation.
• Inputs:
  • usdc_amount (number) — USDC amount (must be > 0)
  • recipient (string) — on-chain address or ENS/BaseName (e.g., example.eth or alice.bnb)
• Output (typical):
  • status: “scheduled”
  • scheduled_tx_id or tx_hash (if immediately available)
  • transaction_link: URL to view transaction on BaseScan
  • message: human-readable note

Example request payload (MCP/function-style):

{
  "name": "transfer-usdc",
  "arguments": {
    "usdc_amount": 12.5,
    "recipient": "alice.eth"
  }
}

2. create_coinbase_mpc_wallet

• Description: Create a Coinbase MPC wallet and persist recovery info. If a wallet already exists, returns the existing wallet address.
• Behavior:
  • Calls Coinbase CDP to create / retrieve wallet
  • Saves wallet metadata (seed info) to Documents/mpc_info.json
• Output (typical):
  • wallet_address: 0x…
  • created: true | false
  • file: path to mpc_info.json

Example request payload:

{
  "name": "create_coinbase_mpc_wallet",
  "arguments": {}
}

Use Cases

• Reimbursements and refunds: An e-commerce backend or customer service agent can schedule a USDC refund to a buyer’s ENS or Base address without exposing gas to the recipient.

  • Example: schedule 25.00 USDC to “customer123.eth” as a refund receipt.

• Tipping or rewards: Content platforms or bots can tip creators instantly (scheduled) using a secure MPC signing flow.

  • Example: transfer 1.00 USDC to “creator.basenet” after a milestone is reached.

• Payroll or payouts: Distribute micro-payments or stipend batches without requiring recipients to pay gas.

  • Example: batch-schedule many small USDC transfers to contributors’ ENS names.

• Onboarding and testing: Developers can programmatically create MPC wallets for test flows and verify the scheduling behavior before integrating into production.

Security