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.
