Mint Club V2 MCP Server

An MCP server exposing Mint Club V2 Bond operations and bounded local Uniswap ZapV2 routing across ten mainnets and two testnets.

npm package · repository · CLI reference · ElizaOS plugin

The server delegates to @mint.club/v2-cli, so the CLI remains the single source of truth for contracts, token resolution, route discovery, pricing, and transactions. Chain keys are loaded from the CLI's published chain-registry.json rather than duplicated in the MCP package.

Configure

Requires Node.js 18 or later. Most MCP clients can launch the package directly with npx:

{
  "mcpServers": {
    "mintclub": {
      "command": "npx",
      "args": ["-y", "@mint.club/v2-mcp@2"]
    }
  }
}

For a global installation, run npm install -g @mint.club/v2-mcp and use "command": "mintclub-mcp" instead. The MCP package installs a compatible @mint.club/v2-cli 2.x runtime dependency automatically.

Read-only tools work without a wallet. Write tools and wallet_balance require PRIVATE_KEY in the server process, or a key in ~/.mintclub/.env. Supply it through the MCP client's secret/environment facility. To generate a dedicated local wallet, install the CLI and run mc wallet --generate in a trusted terminal.

Never store a key in a committed MCP configuration or paste it into a model conversation. Use a dedicated wallet with limited funds.

Every write tool requires an explicit chain and the literal structured argument "confirm": true. This field prevents accidental omission but is not proof of user authorization: configure the MCP host to require interactive approval for tools marked destructive. The client must show the complete chain, assets, amounts, and limits before setting it; the server never infers confirmation.

Tools

The server exposes nine protocol-specific tools:

| Tool | Description | |---|---| | token_info | Token supply, reserve, curve, price, and USD values | | token_price | Price in reserve token and USD | | wallet_balance | Chain-local configured-wallet balances | | buy_token | MCV2_Bond.mint with reserve ERC-20 | | sell_token | MCV2_Bond.burn for reserve ERC-20 | | zap_buy | Exact routed input asset → MCV2_ZapV2.zapMint | | zap_sell | MCV2_ZapV2.zapBurn → routed output asset | | send_token | Send native currency or an ERC-20 token | | create_token | Create an ERC-20 bonding curve token |

create_token requires curve, initialPrice, and finalPrice in addition to its name, symbol, reserve, and maximum supply. It uses the CLI defaults of 100 basis points (1%) for both mint and burn royalties; use the CLI directly when different royalties are required.

Read tools accept an optional canonical chain property and default to Base. Every write tool requires chain explicitly. Supported values are:

ethereum · optimism · arbitrum · avalanche · base · polygon · bsc · zora · unichain · robinhood · sepolia · base-sepolia

Blast is unsupported by this integration.

send_token also requires an explicit token asset. Use the literal "NATIVE" for the selected chain's native currency; otherwise provide an ERC-20 symbol or address.

ZapV2 inputs

zap_buy requires:

{
  "chain": "arbitrum",
  "token": "0xMINT_CLUB_TOKEN",
  "inputToken": "USDT",
  "inputAmount": "10",
  "slippage": "1",
  "confirm": true
}

Optional minTokens is denominated in the Mint Club token. inputAmount is exact.

zap_sell requires:

{
  "chain": "unichain",
  "token": "0xMINT_CLUB_TOKEN",
  "amount": "100",
  "outputToken": "USDC",
  "slippage": "1",
  "confirm": true
}

Optional minOutput is denominated in the output asset. amount is the exact Mint Club token burn amount.

The Mint Club token passed to zap_buy or zap_sell may be ERC-20 or ERC-1155; ERC-1155 amounts must be whole numbers. Routed input and output assets must be native currency or ERC-20 tokens.

The CLI enumerates direct and one-intermediary homogeneous V2/V3/V4 candidates where configured, selects the greatest exact-input output among those candidates, and encodes it with the Universal Router SDK. It does not call an external routing API and does not claim global route optimality.

ZapV2 is deployed on every supported chain listed above. Deployment addresses are maintained by @mint.club/v2-cli; see the CLI contract table.

Example requests

• “Get token info for SIGNET on Base.” → token_info
• Confirmed buy_token call for 100 TOKEN on Robinhood with "confirm": true.
• Confirmed zap_buy call using exactly 10 USDT on Arbitrum with "confirm": true.
• Confirmed zap_sell call for 50 TOKEN to USDC on Unichain with "confirm": true.
• Confirmed create_token call for My Token (MYT), backed by USDG on Robinhood, with maximum supply 1,000,000, a linear curve from 0.01 to 1 USDG, and "confirm": true.

Safe CLI execution

Tool arguments are passed to mc with execFileSync argv arrays. User values are not interpolated into a shell command. The server appends CLI --yes only after validating confirm === true for a write tool.

Set MINTCLUB_CLI to override the CLI executable path.

Development

From the repository root:

npm ci
npm --prefix mcp run check
npm --prefix mcp test
npm --prefix mcp run build

License

MIT. Published tarballs include the project LICENSE and generated THIRD_PARTY_NOTICES.md covering every package bundled into the MCP server.