TokenTool MCP

Deploy and manage compliant tokens from Claude, Cursor, or any AI agent — by typing a sentence.

Built on Bitbond TokenTool — 8,300+ deployments, CertiK-audited contracts, compliance built in.

See It in Action

"Deploy a token called Green Bond A, 1M supply on Base, with whitelist and pausable."

→ CertiK-audited ERC-20 deployed on-chain in ~30 seconds. Contract address returned. No Solidity required.

Install

Claude Desktop

Add to `~/.claude/claude_desktop_config.json`:

{
  "mcpServers": {
    "token-tool": {
      "command": "npx",
      "args": ["-y", "token-tool-mcp"],
      "env": {
        "BITBOND_PRIVATE_KEY": "0x..."
      }
    }
  }
}

Cursor

**→ One-click install for Cursor**

Or add manually to `.cursor/mcp.json`:

{
  "mcpServers": {
    "token-tool": {
      "command": "npx",
      "args": ["-y", "token-tool-mcp"],
      "env": {
        "BITBOND_PRIVATE_KEY": "0x..."
      }
    }
  }
}

VS Code

**→ One-click install for VS Code**

Or add to `.vscode/mcp.json` in your workspace:

{
  "servers": {
    "token-tool": {
      "command": "npx",
      "args": ["-y", "token-tool-mcp"],
      "env": {
        "BITBOND_PRIVATE_KEY": "0x..."
      }
    }
  }
}

Claude Code

claude mcp add token-tool -- npx -y token-tool-mcp

Then set your key in the environment: `export BITBOND_PRIVATE_KEY=0x...`

Example Prompts

Once connected, try these:

Tools

17 tools across the full token lifecycle:

Supported Networks

EVM (8): Ethereum · Polygon · BNB Chain · Arbitrum · Base · Optimism · Avalanche · Peaq

Non-EVM (2): Solana (SPL tokens) · Stellar (Stellar assets)

Testnets (5): Sepolia · Base Sepolia · BNB Testnet · Solana Devnet · Stellar Testnet

Human-friendly aliases work everywhere: `eth`, `polygon`, `bnb`, `arb`, `base`, `op`, `avax`, `peaq`, `sol`, `stellar`

Compliance Features

Optional flags on every deployment — the features institutional issuers and RWA platforms need:

How It Works

You (natural language) → MCP Client (Claude/Cursor/VS Code) → TokenTool MCP Server (local)
    → Bitbond TokenTool API → Smart contract factory → On-chain deployment

1. You type a prompt in your MCP client

2. The client calls the appropriate tool on the local MCP server (stdio transport — nothing leaves your machine until step 3)

3. The MCP server constructs a deployment transaction and submits it to Bitbond's TokenTool smart contract factory on the target chain

4. The factory deploys a CertiK-audited ERC-20 contract with your parameters

5. The contract address and transaction hash are returned to your MCP client

Your private key signs transactions locally. It is read from an environment variable, never passed as an argument, and never transmitted to Bitbond or any third party. The MCP server itself is stateless — the only local state is an optional deployment registry at `data/registry.json`.

CLI

TokenTool MCP also works as a standalone CLI for scripts, CI/CD, and non-MCP agents:

# List all supported chains
token-tool chains

# Estimate cost before deploying
token-tool cost --chain base

# Deploy a token
token-tool deploy \
  --chain base \
  --name "My Token" \
  --symbol MTK \
  --supply 1000000 \
  --mintable \
  --pausable

# Post-deployment management
token-tool mint --chain base --address 0x... --to 0x... --amount 500000
token-tool burn --chain base --address 0x... --amount 10000
token-tool pause --chain base --address 0x...
token-tool info --chain base --address 0x...

# View your deployment history
token-tool registry

All commands output structured JSON. Install globally with `npm install -g token-tool-mcp` to use `token-tool` directly.

Deploy Flags

Security

• Private key stays local. Read from `BITBOND_PRIVATE_KEY` env var only — never passed as a CLI argument, never logged, never transmitted
• stdio transport. The MCP server communicates with your client locally. No network listener, no open ports
• CertiK-audited contracts. You're deploying battle-tested smart contracts, not generated Solidity
• Testnet by default. We recommend starting on Sepolia or Base Sepolia — it's free and functionally identical to mainnet
• Human-in-the-loop. For mainnet deployments ($299 each), enable confirmation prompts in your MCP client before executing transactions

Pricing

The $299 fee is Bitbond's standard TokenTool pricing — the same whether you deploy via the web UI, the API, or this MCP server. It's paid in the chain's native token (ETH, MATIC, BNB, etc.) at the time of deployment. No subscription, no API key, no per-call charges.

Architecture

token-tool-mcp/
├── src/
│   ├── index.js          ← MCP server (stdio transport)
│   ├── cli.js            ← CLI interface
│   ├── tokenTool.js      ← Core engine (shared by CLI + MCP)
│   ├── chains.js         ← Network registry + aliases
│   ├── solana.js         ← SPL token adapter
│   └── stellar.js        ← Stellar asset adapter
├── data/
│   └── registry.json     ← Local deployment history
├── SKILL.md              ← OpenClaw agent skill descriptor
├── CHANGELOG.md
└── README.md

Built on TokenTool

Bitbond TokenTool is one of the most widely used token deployment platforms in Web3:

• 8,300+ tokens deployed across production networks
• CertiK-audited smart contracts — audit report
• Used by enterprises, DAOs, and developers in 50+ countries
• Live since 2020, maintained by Bitbond GmbH (Berlin)

TokenTool MCP wraps this same production infrastructure for AI agents.

Contributing

git clone https://github.com/thendrix-eng/token-tool-mcp
cd token-tool-mcp
npm install
node src/index.js   # start MCP server
node src/cli.js     # run CLI

Issues and PRs welcome.

License

MIT — Bitbond GmbH