Grip MCP
OfficialProvides tools for managing a non-custodial USDC wallet on Base using Coinbase Smart Wallet, enabling AI agents to create and settle payments with human approval.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Grip MCP Show me my Grip wallet"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Grip MCP
Give Claude (or any MCP-compatible agent) a non-custodial USDC wallet on Base — with human-in-the-loop approval on every payment.
What this is
@grip-foundation/grip-mcp is a Model Context Protocol server that exposes four tools to any MCP-aware client (Claude Desktop, Claude Code, Continue, etc.):
Tool | What it does | Who approves |
| Returns the agent's smart account address + USDC balance on Base. | — |
| Stages a payment (off-chain). Returns an approval token. | — |
| Settles or rejects a staged payment. On approve, executes a real USDC transfer on Base mainnet. | Human, in chat |
| Lists recent payments from the session. | — |
The agent never moves money without you. The flow is: agent stages → you confirm in chat → agent settles. There is no programmatic auto-approve.
Related MCP server: @arispay/payagent-mcp
Install
Option 1 — via npx (after first publish)
In ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"grip": {
"command": "npx",
"args": ["-y", "@grip-foundation/grip-mcp"]
}
}
}Option 2 — local clone
git clone https://github.com/grip-foundation/grip-mcp.git
cd grip-mcp
pnpm install
pnpm run buildThen point Claude Desktop at the built file:
{
"mcpServers": {
"grip": {
"command": "node",
"args": ["/absolute/path/to/grip-mcp/dist/server/index.js"]
}
}
}Restart Claude Desktop after editing the config.
First run
The first time the server starts, it generates a brand-new EOA private key and stores it at ~/.grip-mcp/agent-key (mode 0600). This key controls the smart account.
In Claude, ask:
Show me my Grip wallet
Claude will call grip_wallet and reply with your smart account address, balance, and limits. Send USDC on Base to that address to fund.
Making a payment
Once funded, ask Claude something like:
Send 5 USDC to 0xba14744FfD57FA7d03b20D4c8BeDAaC301E865d1
Claude will:
Call
grip_create_paymentto stage the payment off-chain.Show you the details (amount, recipient, memo) and ask for confirmation.
Wait for your reply.
If you say "approve" → call
grip_settle_payment(token, "approve")→ executes on Base.If you say "no" → call
grip_settle_payment(token, "reject")→ no on-chain action.
Tx hash + Basescan link are returned on settlement.
Configuration
Env var | Default | What it does |
| (auto-generate) | Override the agent's signer private key. Useful for restoring a wallet across machines. |
|
| Where the auto-generated key is stored. |
|
| Maximum USDC per single payment. |
|
| Maximum USDC across all payments per UTC day. |
Security model
Non-custodial. The Grip Foundation does not hold your keys, your USDC, or any record of your payments. Everything runs on your machine.
Managed paymaster, no signup. Gas is paid in USDC via the Pimlico paymaster routed through Grip's hosted proxy. You don't need a Pimlico account.
Human-in-the-loop is enforced by the protocol, not the model.
grip_create_paymentonly stages.grip_settle_paymentis a separate tool call. Most MCP clients (Claude Desktop included) prompt for human confirmation before executing tool calls — that's a second layer of gating.Caps are enforced server-side. Even if the model attempts a payment over your per-tx or daily cap, the server refuses to stage it.
Architecture
Claude Desktop
│ MCP (stdio)
▼
grip-mcp (this server)
│ @grip-labs/sdk
▼
Grip-managed paymaster proxy → Pimlico bundler → Base mainnet
▲
Coinbase Smart Wallet
(your smart account)The smart account is a Coinbase Smart Wallet (ERC-4337) on Base. The first payment from a fresh wallet runs a one-time bootstrap UserOp that deploys the account and approves the paymaster for USDC reimbursement; subsequent UserOps are USDC-paid.
Known issues
First payment may need a retry. In @grip-labs/sdk@0.4, the bootstrap UserOp (deploy + paymaster approve) and the actual transfer UserOp are submitted as two separate operations. There's a small race window where viem's internal getFactoryArgs() reads stale getCode from the public RPC after bootstrap has settled at the Pimlico bundler — viem then includes initCode in the second UserOp and the bundler rejects it with AA10 sender already constructed.
If your first payment fails with that error, simply ask the agent to retry. The retry succeeds because the on-chain state has propagated by then. Subsequent payments from the same wallet are clean — bootstrap runs at most once per wallet.
A fix is shipping in @grip-labs/sdk@0.5 that consolidates bootstrap + first transfer into a single sponsored UserOp using executeBatch, eliminating the race by construction and saving ~30% gas on the first payment. grip-mcp will pick it up in 0.1.1.
License
MIT
Built by
Grip Foundation · open identity + payments rails for AI agents.
Available Tools
4 toolsgrip_create_paymentCreate a pending payment (requires human approval)A
Stages a payment from the agent's Grip wallet to a recipient. DOES NOT execute on-chain. Returns an approval_token. You MUST then show the payment details (amount, recipient, memo) to the human in plain language and ASK FOR EXPLICIT CONFIRMATION before calling grip_settle_payment. Never auto-approve. The human must say 'approve' (or equivalent) before settling. If they say 'no', call grip_settle_payment with decision='reject'.
Inputs: recipient (required), amount_usdc (required), memo.
grip_list_paymentsList recent payments from this sessionARead-onlyIdempotent
Returns recent payments (pending, settled, rejected, failed) staged or executed in this MCP session. Read-only. Useful when the human asks 'what have I paid today' or 'what's pending'.
Inputs: limit.
grip_settle_paymentSettle (or reject) a pending paymentADestructiveIdempotent
Executes the on-chain transfer for a previously-staged payment, or marks it as rejected. ONLY call this after the human has explicitly confirmed (or declined) the payment in plain language. If the human has not confirmed, do not call this tool. On approve, this performs a real USDC transfer on Base mainnet via the Pimlico paymaster — it is irreversible.
Inputs: approval_token (required), decision (required).
grip_walletGet the agent's Grip wallet infoARead-onlyIdempotent
Returns this agent's Grip Pay wallet address (Base mainnet smart account) and current USDC balance. Use this when the human asks about the wallet, where to fund it, how much USDC the agent has, or before suggesting any payment.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clear, distinct purpose: creating staged payments, listing payments, settling/rejecting, and checking wallet info. No overlap or ambiguity.
All tools start with 'grip_' and most follow a verb_noun pattern (create_payment, list_payments, settle_payment). The exception is 'grip_wallet', which is a noun phrase, but the inconsistency is minor given the small set.
Four tools is well-scoped for a payment/wallet MCP server. It covers staging, settling, listing, and wallet info without being too few or excessive.
The tool surface covers the core payment workflow: create, settle/reject, list, and wallet info. A potential minor gap is lack of explicit cancellation for staged payments, but the reject option in settle effectively handles that.
Maintenance
Related MCP Connectors
Give AI agents a wallet with a spending limit. Non-custodial USDC on Base, server-enforced limits.
Self-custodial USDC wallet on Base for AI agents: on-chain caps, Face ID, one-tap pause.
Shared USDC wallets for agents and teams, with optional write access and human-signed payments.
Monetization and execution gateway for autonomous AI agents on Base Mainnet
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI agents to manage USDC wallets on Solana, allowing them to send payments, create invoices, and access paid APIs within human-defined spending limits. It uses threshold signatures to provide agents with financial autonomy while ensuring secure oversight and transaction approval.3670 npm4Apache 2.0

@arispay/payagent-mcpofficial
AlicenseAqualityBmaintenanceEnables AI agents to call paid APIs and settle HTTP 402 payment challenges with USDC on Base, without private keys ever being involved.7265 npmMIT- AlicenseAqualityDmaintenanceProvides AI agents with a wallet and access to 900+ pay-per-call intelligence APIs across 74 verticals, with automatic USDC payments on Base and built-in spend guardrails.5110 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to make non-custodial USDC payments on Base through an MCP endpoint, with server-enforced per-payment and daily caps, human approval bands, and recipient allowlists.739 npmMIT