Mint Club V2 — AI Tools

Provides a Mint Club V2 MCP server for token creation, pricing, and swapping through CLI, agents, and plugins.

javascript

3

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "steemhunt-mint.club-v2-ai": {
      "command": "npx",
      "args": [
        "-y",
        "mintclub-mcp"
      ],
      "env": {
        "PRIVATE_KEY": "YOUR_PRIVATE_KEY"
      }
    }
  }
}

Mint Club V2 MCP Server enables programmatic access to Mint Club’s bonding curve tooling through a server that runs locally or remotely. You can interact with token creation, pricing, minting, burning, and asset swaps via a standardized MCP interface, powering CLI, AI assistants, and autonomous agents to operate Mint Club V2 on Base without manual UI steps.

How to use

You will run the MCP server locally and connect your Claude Cursor or other MCP clients to it. This server exposes tooling to query token details, obtain prices, manage wallets, execute token swaps, and create or bond tokens using Mint Club V2’s bonding curve contracts.

How to install

Prerequisites you need before starting are Node.js and npm. You should also have a compatible MCP client capable of consuming the MCP server you run.

Step 1: Install the MCP server command locally.

Step 2: Start the MCP server using the provided command. Step 3: Point your MCP client to the running server configuration.

"mcpServers": {
  "mintclub": {
    "command": "npx",
    "args": ["-y", "mintclub-mcp"],
    "env": { "PRIVATE_KEY": "0x..." }
  }
}

Configuration and usage notes

The MCP server is configured to run as a local stdio server. You provide the runtime command and arguments, along with any required environment variables. Use the code block above as a template to set up your MCP client configuration.

Troubleshooting tips

If your MCP client cannot connect, verify that the command is installed, the environment variable PRIVATE_KEY is correct, and the process is running. Check that you are using the same port or IPC channel as your MCP client expects and that there are no firewall rules blocking local communication.

Notes on tools exposed by the MCP server

The server exposes a suite of tools to interact with Mint Club V2 tokens and pricing. Tools include token_info, token_price, wallet_balance, buy_token, sell_token, swap, zap_buy, zap_sell, send_token, and create_token. Each tool corresponds to a specific action in the bonding curve ecosystem, enabling end-to-end token management from the MCP interface.

Security considerations

Keep your PRIVATE_KEY secure. Do not expose secret keys in client configurations or logs. Rotate credentials if you suspect exposure and scope access to only what is necessary for your automation workflows.

Available tools

token_info

Fetches detailed information about a specific token, including supply, reserves, and bonding curve parameters.

token_price

Retrieves the current price for minting or burning a token on the bonding curve.

wallet_balance

Checks the balance of a wallet on the configured reserve asset and minted token holdings.

buy_token

Mints new tokens by executing a bonding curve buy operation against the reserve asset.

sell_token

Sells minted tokens back to the bonding curve, redeeming the reserve asset.

swap

Performs a swap between assets, routing through the bonding curve when applicable.

zap_buy

Executes a combined swap and mint in a single transaction for convenience.

zap_sell

Executes a combined burn and swap to liquidate tokens for a different asset.

send_token

Transfers minted tokens from one wallet to another.

create_token

Creates a new bonding curve token with a specified reserve, supply and pricing curve.