How do I install Token Tool?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Token Tool need an API key?

The publisher lists these environment variables: BITBOND_PRIVATE_KEY.

What transport does Token Tool use?

Token Tool runs locally over stdio.

When was Token Tool last checked?

Last checked 2026-11-09. Deploy compliant ERC-20 tokens from any AI agent. 17 tools, 10 networks, CertiK-audited.

Token Tool MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

BITBOND_PRIVATE_KEY — Private key for the wallet used to deploy tokens (hex, with 0x prefix)

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1BITBOND_PRIVATE_KEY=<secret> claude mcp add io.github.bitbond-token-tool -- npx -y token-tool-mcp@1.1.1

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.bitbond-token-tool": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "BITBOND_PRIVATE_KEY": "<secret>"11      }12    }13  }14}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.1.1
API key

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

TokenTool MCP

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

Built on Bitbond TokenTool: 7,000+ tokens deployed, CertiK-audited contracts, issuer controls (allowlist, blocklist, pause, force transfer) 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:

Prompt	What happens
"Deploy a governance token called DAO Vote, 10M supply on Polygon, mintable and burnable"	Deploys an audited ERC-20 with mint + burn enabled
"Estimate the cost to deploy on Arbitrum vs Base"	Returns gas + fee estimates for both chains
"Mint 500K more tokens to 0x1234..."	Mints to target address, confirms tx
"Pause all transfers on contract 0xabcd..."	Activates the emergency stop
"Show me everything I've deployed"	Lists all tokens from local registry
"Deploy an RWA security token on Ethereum with whitelist, force transfer, and document URI linking to the prospectus"	Security-style token with investor transfer restrictions and an on-chain legal document reference

Tools

17 tools across the full token lifecycle:

Tool	Description
`deploy_token`	Deploy a CertiK-audited ERC-20 with optional issuer controls
`estimate_cost`	Quote deployment cost (gas + fee) before committing funds
`list_chains`	List supported networks (10 production, 5 testnets) with chain IDs and aliases
`get_token_info`	Live on-chain token state — name, symbol, supply, paused status, owner
`list_deployed_tokens`	Full local deployment registry
`mint_tokens`	Mint additional supply to any address
`burn_tokens`	Permanently destroy tokens
`pause_token`	Emergency stop — halt all transfers immediately
`unpause_token`	Resume transfers after a pause
`transfer_tokens`	Send tokens to any address
`get_wallet_info`	Deployer wallet address and native balance
`add_to_whitelist`	Add addresses to token whitelist (batch supported)
`remove_from_whitelist`	Remove addresses from token whitelist
`get_whitelist`	View whitelist status and all whitelisted addresses
`add_to_blacklist`	Block an address from token interactions
`remove_from_blacklist`	Unblock a previously blacklisted address
`get_compliance_status`	Check whitelist and blacklist configuration for a token

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

Issuer Controls

Optional flags on every deployment, the controls institutional issuers and RWA platforms ask for. They are tools for an issuer's own compliance process; the token itself does not make an offering compliant.

Feature	Flag	What it does
Whitelist	`--whitelist`	Only approved addresses can hold or receive tokens
Blacklist	`--blacklist`	Block specific addresses from any interaction
Pausable	`--pausable`	Owner can freeze all transfers instantly
Force Transfer	`--force-transfer`	Owner can move tokens between addresses (regulatory recovery)
Document URI	`--document-uri`	Attach a prospectus, term sheet, or legal document on-chain
Max Supply Cap	`--max-supply`	Hard ceiling on total supply, enforced at the contract level

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

You type a prompt in your MCP client
The client calls the appropriate tool on the local MCP server (stdio transport — nothing leaves your machine until step 3)
The MCP server constructs a deployment transaction and submits it to Bitbond's TokenTool smart contract factory on the target chain
The factory deploys a CertiK-audited ERC-20 contract with your parameters
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

Flag	Description
`--chain`	Target network (see aliases above)
`--name`	Token name
`--symbol`	Token symbol
`--supply`	Initial supply (human-readable, e.g. `1000000`)
`--decimals`	Decimal places (default: 18)
`--mintable`	Enable minting after deployment
`--burnable`	Enable burning
`--pausable`	Enable pause/unpause
`--whitelist`	Enable whitelist-only transfers
`--blacklist`	Enable address blacklisting
`--force-transfer`	Enable owner-initiated forced transfers
`--document-uri`	Attach a document URL on-chain
`--max-supply`	Hard cap on total token supply
`--owner`	Token owner address (defaults to deployer)

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 ($499 each, see Pricing), enable confirmation prompts in your MCP client before executing transactions

Pricing

Environment	Cost
Testnet (Sepolia, Base Sepolia, BNB Testnet)	Gas only (~free)
Mainnet (all production chains)	$499 flat fee per deployment + gas

The MCP deploys TokenTool's asset token contract (the one with allowlist, blocklist, force transfer and document URI), so the fee matches Create Asset Token on the TokenTool pricing page, the same whether you deploy via the web UI, the API, or this MCP server. estimate_cost returns the live quote before you commit. 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

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Token Tool?

Does Token Tool need an API key?

What transport does Token Tool use?

When was Token Tool last checked?

Documentation

TokenTool MCP

Built on Bitbond TokenTool: 7,000+ tokens deployed, CertiK-audited contracts, issuer controls (allowlist, blocklist, pause, force transfer) built in.

See It in Action

Install

Claude Desktop

Cursor

VS Code

Claude Code

Example Prompts

Tools

Supported Networks

Issuer Controls

How It Works

CLI

Deploy Flags

Security

Pricing

Architecture

Built on TokenTool

Contributing

License