Coinbase
Coinbase is a platform for buying, selling, transferring, and storing cryptocurrency.
Verdict
Common use cases
- Check test wallet balances during development
- Audit deployment addresses before mainnet launch
- Share wallet details with team in standup
- Verify wallet creation in onboarding flows
- Document wallet addresses for compliance review
Integration
- Vendor
- Coinbase
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 1
- Composio slug
coinbase
Tools
- List Wallets
Retrieve all wallets from coinbase via the cdp sdk.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations page. 2. Find Coinbase in the MCP directory and click Connect. 3. You'll be prompted to paste a Coinbase Developer Platform API key — generate one by logging into the Coinbase Developer Portal, creating a new API key under your project settings, and copying the key string. 4. Paste the key into Switchy's auth dialog and click Authorize. 5. Switchy will verify the connection by attempting to list wallets; if successful, you'll see a confirmation message. 6. Open any Space and type '@Coinbase list my wallets' to test — the MCP should return wallet addresses and metadata from your CDP account. 7. If the connection fails, double-check that your API key has the correct permissions enabled in the Coinbase Developer Portal.
What teammates see: by default, memories from Coinbase are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Wallets
@Coinbase list all wallets in my account and show me their addresses and current status.Open in a Space →
Find Test Wallets
@Coinbase show me all wallets that are set up for testnet, including their network and balance.Open in a Space →
Wallet Count Check
@Coinbase how many wallets do I have in total, and can you group them by network?Open in a Space →
Recent Wallet Activity
@Coinbase list the five most recently created wallets and tell me when they were set up.Open in a Space →
Wallet Address Export
@Coinbase give me a plain list of all wallet addresses, one per line, so I can copy them into our deployment doc.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Coinbase list all my wallets and show their current balances in USD
Found 3 wallets in your Coinbase account: 1. **Main Wallet** (0x742d...89a3) - ETH: 0.45 ($1,125.00) - USDC: 2,500.00 ($2,500.00) 2. **Trading Wallet** (0x8f1c...2b7e) - BTC: 0.012 ($780.00) - ETH: 0.08 ($200.00) 3. **Savings Wallet** (0x3a9d...4c1f) - USDC: 10,000.00 ($10,000.00) Total portfolio value: $14,605.00 (as of current market prices). Note that balances reflect on-chain state and may take 1-2 minutes to update after recent transactions.
This example demonstrates the MCP's core read capability via the Coinbase Developer Platform SDK. Requires API key with 'wallet:read' scope. Balance data is fetched in real-time but USD conversions depend on current market rates. The MCP returns wallet addresses and holdings but does not execute trades or transfers — it's strictly read-only access to your account state.
@Coinbase compare the gas fees on my Ethereum wallets over the last 7 days and identify which one has been most cost-efficient
Analyzed transaction history across your 2 Ethereum wallets: **Main Wallet** (0x742d...89a3): 12 transactions, $47.80 total gas - Average: $3.98/tx - Peak: $8.20 (Tuesday 3pm UTC) **Trading Wallet** (0x8f1c...2b7e): 8 transactions, $52.40 total gas - Average: $6.55/tx - Peak: $11.30 (Wednesday 9am UTC) Main Wallet is 39% more cost-efficient. Trading Wallet's higher fees correlate with transactions during US market hours when network congestion spikes. Consider batching Trading Wallet operations or scheduling them during off-peak periods (weekends, late UTC hours).
This synthesis example pairs wallet data retrieval with AI reasoning to surface actionable insights. The MCP fetches raw transaction logs; the AI calculates averages and identifies patterns. Useful for cost optimization but limited by the 7-day window that Coinbase's API typically exposes for free-tier accounts. Does not access mempool data or predict future gas prices.
@Coinbase show me which wallets hold stablecoins and calculate what percentage of my total portfolio is in stable assets
Stablecoin holdings across your wallets: **Main Wallet**: USDC 2,500.00 ($2,500.00) **Savings Wallet**: USDC 10,000.00 ($10,000.00) Total stablecoins: $12,500.00 Total portfolio value: $14,605.00 **Stable asset allocation: 85.6%** Your portfolio is heavily weighted toward stablecoins, which minimizes volatility but limits upside exposure. The remaining 14.4% is split between ETH (9.1%) and BTC (5.3%). This allocation suggests a conservative risk profile — consider whether this matches your investment timeline and goals.
Demonstrates filtering wallet data by asset type and performing portfolio-level calculations. The MCP retrieves all wallet balances; the AI identifies stablecoins (USDC, USDT, DAI, etc.) and computes percentages. Accuracy depends on correct asset classification — exotic or wrapped stablecoins may not be recognized. This is analysis only; the MCP cannot rebalance your portfolio or execute swaps.
Use-case deep-dives
When Coinbase MCP makes sense for finance teams tracking wallet balances
A 6-person fintech startup holds operating funds across three Coinbase wallets (USD, USDC, and a cold-storage reserve). Their finance lead runs a weekly reconciliation against their accounting system. The Coinbase MCP works here because the team needs read-only wallet visibility without touching the Coinbase web UI, and the single List Wallets tool is enough to pull balances into a Switchy prompt that cross-checks against QuickBooks exports. The API key auth means the finance lead controls access without sharing login credentials. This breaks down if you need transaction history or on-chain data—the MCP only lists wallets, so any deeper audit trail requires the full Coinbase API or a blockchain explorer. If your reconciliation is just 'do we have the cash we think we have,' this MCP is the fastest path.
Why this MCP is too narrow for support ticket workflows
A 12-person crypto exchange's support team fields tickets about missing deposits and withdrawal delays. They want to check customer wallet status without leaving their ticketing system. The Coinbase MCP doesn't fit this scenario. The List Wallets tool only surfaces the company's own wallets, not customer accounts, and it provides no transaction or transfer data. Support agents would still need to pivot to the Coinbase dashboard or a custom integration to answer 'where is my deposit.' The MCP is built for internal treasury visibility, not customer-facing operations. If your support workflow requires per-user wallet inspection or transaction tracing, you need the full Coinbase API or a purpose-built support integration. This MCP saves time only if your team is checking your own wallet inventory, not investigating customer issues.
When one-tool MCPs win for lightweight monitoring rituals
A 4-person DeFi protocol team starts each standup by confirming their treasury wallets are intact (no unexpected transfers, balances match expectations). The Coinbase MCP is ideal here because the ritual is simple: one person asks Switchy 'list our Coinbase wallets,' scans the output, and moves on. The single-tool scope is a feature, not a bug—there's no decision fatigue about which tool to invoke, and the API key setup takes under five minutes. This works only if your monitoring needs stop at wallet enumeration. If the team needs alerts on balance changes, transaction logs, or multi-chain visibility, the MCP becomes a dead end and you're better off with a monitoring service or the full SDK. For a quick daily sanity check, though, this MCP is the right size.
Frequently asked
What does the Coinbase MCP do in Switchy?
It connects your team's Coinbase Developer Platform account so AI agents can query wallet data through the CDP SDK. Right now it exposes one tool: listing all wallets tied to your API key. You'd use this when building crypto treasury dashboards, wallet monitoring workflows, or any automation that needs to know which wallets exist under your account.
Do I need a Coinbase Developer Platform API key?
Yes. You generate an API key from the Coinbase Developer Platform console, then paste it into Switchy's connection flow. The key must have read permissions for wallets. If you're on a team plan at Coinbase, make sure the key is scoped to the right organization — Switchy will only see wallets that key can access.
Can it send transactions or create new wallets?
No. The current tool only lists wallets; it doesn't write anything. If you need to initiate transfers, mint tokens, or provision wallets, you'll still use Coinbase's API directly or their web console. This MCP is read-only for now, which keeps the security surface small when you're just monitoring balances or addresses.
Why use this instead of calling the Coinbase API myself?
You skip the boilerplate. The MCP wraps the CDP SDK so your AI agents can ask "list my wallets" in plain English instead of you writing fetch calls and parsing JSON. It's faster for prototyping dashboards or Slack bots that need wallet context. For production apps with complex logic, the raw API gives you more control.
Who on the team should connect the Coinbase MCP?
Whoever manages your Coinbase Developer Platform account and can generate API keys. That's usually an engineer or finance lead with admin access. Once connected, anyone in your Switchy workspace can invoke the wallet-listing tool in their prompts — the API key is shared across the team, so treat it like you would any credential.