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 "Install 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 MCPShow 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: pay-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.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables 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.63693Apache 2.0
- Alicense-qualityBmaintenanceUSDC payments for AI agents on Base. Direct transfers, pre-funded tabs, x402 paywall handling, and service discovery.52MIT
- AlicenseAqualityDmaintenanceGives AI agents a smart-contract wallet on Base (USDC) with 10 stdio tools: create wallets, send USDC payments, pay x402-protected HTTP resources, and run ERC-8183 escrow Jobs for A2A service delivery.106MIT

@arispay/payagent-mcpofficial
AlicenseDqualityFmaintenanceEnables AI agents to call paid APIs and settle HTTP 402 payment challenges with USDC on Base, without private keys ever being involved.2127MIT
Related MCP Connectors
30 pay-per-call APIs for AI agents: compliance, trade, safety, web, data. USDC on Base via x402.
AI-native settlement rail + intelligence oracle for autonomous agents. x402, Base mainnet, 81 tools.
Keyless non-custodial crypto payments for AI agents: payment links and tip jars, no API key.
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/grip-foundation/grip-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server