mcp_tip_md_tip_on_baseLABSCO SUMMARY
A payment rail an agent can actually use.
Tipping normally means a browser, a wallet extension and a chain choice. Here the whole sequence — check balance, pick the chain the recipient supports, send, confirm — happens as tool calls, with the platform's cut taken on the backend.
What it is
The MCP server for tip.md, which routes tips to developers' own wallets. Payments come in from a dedicated tipping wallet over the x402 protocol and go out through Coinbase's CDP wallet API, with a fixed platform fee deducted and the rest disbursed to the recipient.
What you get
- The balance available for tipping, so the agent knows what it can spend before it offers
- A tip sent to a named recipient, with Base and Solana each addressable directly
- A lookup of which wallet types a recipient has configured, so a tip is not sent down a rail they cannot receive on
- Withdrawal of unspent funds from the tipping wallet back to you
- Export of the tipping wallet, and a ping tool for checking the connection is live
Requirements
Clone and npm install, then run. Real tipping needs a funded dedicated tipping wallet; NODE_ENV=demo npm start runs the payment flow in demo mode. The server must be connected to an MCP client to exercise the tools — running it alone only prints logs.
Setup effort
Build from source — clone the repository and build it, then point your client at the built dist/mcp-server/src/index.js
USE CASES
Thanking a maintainer without leaving the conversation
Name the recipient and the amount; the tip is collected from your tipping wallet and disbursed to theirs.
Knowing what you can spend before you offer
Read the tipping balance first, so the agent commits to an amount it can actually send.
Sending on the chain the recipient supports
Check which wallet types they have configured, then send on Base or Solana accordingly rather than guessing.
Getting unspent funds back out
Withdraw what is left in the tipping wallet when the campaign or the session is over.
Checking the connection before a live payment
Ping the server and confirm it responds before putting a real transfer through it.
8 tools
Listed in project docs. Your client may show a different list.
mcp_tip_md_tip_on_solanamcp_tip_md_check_tipping_balancemcp_tip_md_export_tipping_walletmcp_tip_md_withdraw_tipping_fundsmcp_tip_md_get_user_wallet_typesmcp_tip_md_crypto_tippingmcp_tip_md_pingBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation. With NODE_ENV=demo payments are simulated; production needs MongoDB, Coinbase CDP and an x402 wallet key. mcp_tip_md_export_tipping_wallet returns your wallet's private key.
Requires
- node on PATH
- CDP_API_KEY_ID in your environment
- CDP_API_KEY_SECRET in your environment
- X402_WALLET_PRIVATE_KEY in your environment
- MONGODB_URI in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Clone the repository and build it, then point your client at the built dist/mcp-server/src/index.js. This one is built from source rather than installed with a single command.
Server setup
Setup
git clone https://github.com/xR0am/tip-md-x402-mcp-server.git
cd tip-md-x402-mcp-server
npm installDemo mode (no setup required):
NODE_ENV=demo npm startProduction Deployment: npm install, npm run build, npm start — after creating a .env file with MONGODB_URI, CDP_API_KEY_ID, CDP_API_KEY_SECRET and X402_WALLET_PRIVATE_KEY
Connect an MCP client: Cursor starts the server itself from the configuration under MCP Clients. For Claude Desktop the project routes through Supergateway (npm install -g supergateway), which bridges the server's HTTP-stream endpoint at http://localhost:3000/mcp to stdio — start the server first with NODE_ENV=demo npm start.
node
node dist/mcp-server/src/index.jsMCP Clients
Claude Desktop — Supergateway
{
"mcpServers": {
"tip-md-demo": {
"command": "npx",
"args": [
"-y",
"supergateway",
"--httpStream",
"http://localhost:3000/mcp",
"--outputTransport",
"stdio"
]
}
}
}Cursor
{
"mcpServers": {
"tip-md-demo": {
"command": "node",
"args": [
"dist/mcp-server/src/index.js"
],
"cwd": "<YOUR_PATH_TO_TIP_MD_X402_MCP>",
"env": {
"NODE_ENV": "demo"
}
}
}
}<YOUR_PATH_TO_TIP_MD_X402_MCP> is the folder you cloned. Npm install already builds dist/, because the package runs npm run build after installing.
The configuration on this page does not set CDP_API_KEY_ID, CDP_API_KEY_SECRET, X402_WALLET_PRIVATE_KEY and MONGODB_URI; the project's instructions put them in a .env file. To supply them without depending on where the server looks for that file, use the block's "env" section.