{
  "markdown": "# TokenTool MCP\n\n[![npm version](https://img.shields.io/npm/v/token-tool-mcp.svg)](https://www.npmjs.com/package/token-tool-mcp)\n[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)\n[![Node.js ≥18](https://img.shields.io/badge/node-%3E%3D18-brightgreen)](https://nodejs.org)\n[![10 Networks](https://img.shields.io/badge/networks-10-blue)](#supported-networks)\n[![CertiK Audited](https://img.shields.io/badge/contracts-CertiK%20audited-green)](https://tokentool.bitbond.com)\n\n**Deploy and manage compliant tokens from Claude, Cursor, or any AI agent — by typing a sentence.**\n\nBuilt on [Bitbond TokenTool](https://tokentool.bitbond.com) — 8,300+ deployments, CertiK-audited contracts, compliance built in.\n\n<p align=\"center\">\n  <img src=\"https://raw.githubusercontent.com/thendrix-eng/token-tool-mcp/main/assets/demo-final.gif\" alt=\"TokenTool MCP Demo\" width=\"720\">\n</p>\n\n---\n\n## See It in Action\n\n```\n\"Deploy a token called Green Bond A, 1M supply on Base, with whitelist and pausable.\"\n```\n\n→ CertiK-audited ERC-20 deployed on-chain in ~30 seconds. Contract address returned. No Solidity required.\n\n---\n\n## Install\n\n#### Claude Desktop\n\nAdd to `~/.claude/claude_desktop_config.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"token-tool\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"token-tool-mcp\"],\n      \"env\": {\n        \"BITBOND_PRIVATE_KEY\": \"0x...\"\n      }\n    }\n  }\n}\n```\n\n#### Cursor\n\n[**→ One-click install for Cursor**](cursor://anysphere.cursor-deeplink/mcp/install?name=token-tool&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsInRva2VuLXRvb2wtbWNwIl19)\n\nOr add manually to `.cursor/mcp.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"token-tool\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"token-tool-mcp\"],\n      \"env\": {\n        \"BITBOND_PRIVATE_KEY\": \"0x...\"\n      }\n    }\n  }\n}\n```\n\n#### VS Code\n\n[**→ One-click install for VS Code**](https://vscode.dev/redirect/mcp/install?name=token-tool&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22token-tool-mcp%22%5D%7D)\n\nOr add to `.vscode/mcp.json` in your workspace:\n\n```json\n{\n  \"servers\": {\n    \"token-tool\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"token-tool-mcp\"],\n      \"env\": {\n        \"BITBOND_PRIVATE_KEY\": \"0x...\"\n      }\n    }\n  }\n}\n```\n\n#### Claude Code\n\n```bash\nclaude mcp add token-tool -- npx -y token-tool-mcp\n```\n\nThen set your key in the environment: `export BITBOND_PRIVATE_KEY=0x...`\n\n---\n\n## Example Prompts\n\nOnce connected, try these:\n\n| Prompt | What happens |\n|--------|-------------|\n| *\"Deploy a governance token called DAO Vote, 10M supply on Polygon, mintable and burnable\"* | Deploys an audited ERC-20 with mint + burn enabled |\n| *\"Estimate the cost to deploy on Arbitrum vs Base\"* | Returns gas + fee estimates for both chains |\n| *\"Mint 500K more tokens to 0x1234...\"* | Mints to target address, confirms tx |\n| *\"Pause all transfers on contract 0xabcd...\"* | Activates the emergency stop |\n| *\"Show me everything I've deployed\"* | Lists all tokens from local registry |\n| *\"Deploy an RWA security token on Ethereum with whitelist, force transfer, and document URI linking to the prospectus\"* | Full compliance token with investor restrictions and legal doc reference |\n\n---\n\n## Tools\n\n17 tools across the full token lifecycle:\n\n| Tool | Description |\n|------|-------------|\n| `deploy_token` | Deploy a CertiK-audited ERC-20 with optional compliance features |\n| `estimate_cost` | Quote deployment cost (gas + fee) before committing funds |\n| `list_chains` | List all 12 supported networks with chain IDs and aliases |\n| `get_token_info` | Live on-chain token state — name, symbol, supply, paused status, owner |\n| `list_deployed_tokens` | Full local deployment registry |\n| `mint_tokens` | Mint additional supply to any address |\n| `burn_tokens` | Permanently destroy tokens |\n| `pause_token` | Emergency stop — halt all transfers immediately |\n| `unpause_token` | Resume transfers after a pause |\n| `transfer_tokens` | Send tokens to any address |\n| `get_wallet_info` | Deployer wallet address and native balance |\n| `add_to_whitelist` | Add addresses to token whitelist (batch supported) |\n| `remove_from_whitelist` | Remove addresses from token whitelist |\n| `get_whitelist` | View whitelist status and all whitelisted addresses |\n| `add_to_blacklist` | Block an address from token interactions |\n| `remove_from_blacklist` | Unblock a previously blacklisted address |\n| `get_compliance_status` | Check whitelist and blacklist configuration for a token |\n\n---\n\n## Supported Networks\n\n**EVM (8):** Ethereum · Polygon · BNB Chain · Arbitrum · Base · Optimism · Avalanche · Peaq\n\n**Non-EVM (2):** Solana (SPL tokens) · Stellar (Stellar assets)\n\n**Testnets (5):** Sepolia · Base Sepolia · BNB Testnet · Solana Devnet · Stellar Testnet\n\nHuman-friendly aliases work everywhere: `eth`, `polygon`, `bnb`, `arb`, `base`, `op`, `avax`, `peaq`, `sol`, `stellar`\n\n---\n\n## Compliance Features\n\nOptional flags on every deployment — the features institutional issuers and RWA platforms need:\n\n| Feature | Flag | What it does |\n|---------|------|-------------|\n| **Whitelist** | `--whitelist` | Only approved addresses can hold or receive tokens |\n| **Blacklist** | `--blacklist` | Block specific addresses from any interaction |\n| **Pausable** | `--pausable` | Owner can freeze all transfers instantly |\n| **Force Transfer** | `--force-transfer` | Owner can move tokens between addresses (regulatory recovery) |\n| **Document URI** | `--document-uri` | Attach a prospectus, term sheet, or legal document on-chain |\n| **Max Supply Cap** | `--max-supply` | Hard ceiling on total supply, enforced at the contract level |\n\n---\n\n## How It Works\n\n```\nYou (natural language) → MCP Client (Claude/Cursor/VS Code) → TokenTool MCP Server (local)\n    → Bitbond TokenTool API → Smart contract factory → On-chain deployment\n```\n\n1. You type a prompt in your MCP client\n2. The client calls the appropriate tool on the **local** MCP server (stdio transport — nothing leaves your machine until step 3)\n3. The MCP server constructs a deployment transaction and submits it to Bitbond's TokenTool smart contract factory on the target chain\n4. The factory deploys a CertiK-audited ERC-20 contract with your parameters\n5. The contract address and transaction hash are returned to your MCP client\n\n**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`.\n\n---\n\n## CLI\n\nTokenTool MCP also works as a standalone CLI for scripts, CI/CD, and non-MCP agents:\n\n```bash\n# List all supported chains\ntoken-tool chains\n\n# Estimate cost before deploying\ntoken-tool cost --chain base\n\n# Deploy a token\ntoken-tool deploy \\\n  --chain base \\\n  --name \"My Token\" \\\n  --symbol MTK \\\n  --supply 1000000 \\\n  --mintable \\\n  --pausable\n\n# Post-deployment management\ntoken-tool mint --chain base --address 0x... --to 0x... --amount 500000\ntoken-tool burn --chain base --address 0x... --amount 10000\ntoken-tool pause --chain base --address 0x...\ntoken-tool info --chain base --address 0x...\n\n# View your deployment history\ntoken-tool registry\n```\n\nAll commands output structured JSON. Install globally with `npm install -g token-tool-mcp` to use `token-tool` directly.\n\n### Deploy Flags\n\n| Flag | Description |\n|------|-------------|\n| `--chain` | Target network (see aliases above) |\n| `--name` | Token name |\n| `--symbol` | Token symbol |\n| `--supply` | Initial supply (human-readable, e.g. `1000000`) |\n| `--decimals` | Decimal places (default: 18) |\n| `--mintable` | Enable minting after deployment |\n| `--burnable` | Enable burning |\n| `--pausable` | Enable pause/unpause |\n| `--whitelist` | Enable whitelist-only transfers |\n| `--blacklist` | Enable address blacklisting |\n| `--force-transfer` | Enable owner-initiated forced transfers |\n| `--document-uri` | Attach a document URL on-chain |\n| `--max-supply` | Hard cap on total token supply |\n| `--owner` | Token owner address (defaults to deployer) |\n\n---\n\n## Security\n\n- **Private key stays local.** Read from `BITBOND_PRIVATE_KEY` env var only — never passed as a CLI argument, never logged, never transmitted\n- **stdio transport.** The MCP server communicates with your client locally. No network listener, no open ports\n- **CertiK-audited contracts.** You're deploying battle-tested smart contracts, not generated Solidity\n- **Testnet by default.** We recommend starting on Sepolia or Base Sepolia — it's free and functionally identical to mainnet\n- **Human-in-the-loop.** For mainnet deployments ($299 each), enable confirmation prompts in your MCP client before executing transactions\n\n---\n\n## Pricing\n\n| Environment | Cost |\n|-------------|------|\n| **Testnet** (Sepolia, Base Sepolia, BNB Testnet) | Gas only (~free) |\n| **Mainnet** (all production chains) | **$299** flat fee per deployment + gas |\n\nThe $299 fee is Bitbond's standard TokenTool pricing — the same whether you deploy via the [web UI](https://tokentool.bitbond.com), 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.\n\n---\n\n## Architecture\n\n```\ntoken-tool-mcp/\n├── src/\n│   ├── index.js          ← MCP server (stdio transport)\n│   ├── cli.js            ← CLI interface\n│   ├── tokenTool.js      ← Core engine (shared by CLI + MCP)\n│   ├── chains.js         ← Network registry + aliases\n│   ├── solana.js         ← SPL token adapter\n│   └── stellar.js        ← Stellar asset adapter\n├── data/\n│   └── registry.json     ← Local deployment history\n├── SKILL.md              ← OpenClaw agent skill descriptor\n├── CHANGELOG.md\n└── README.md\n```\n\n---\n\n## Built on TokenTool\n\n[Bitbond TokenTool](https://tokentool.bitbond.com) is one of the most widely used token deployment platforms in Web3:\n\n- **8,300+** tokens deployed across production networks\n- **CertiK-audited** smart contracts — [audit report](https://tokentool.bitbond.com)\n- Used by enterprises, DAOs, and developers in **50+ countries**\n- Live since 2020, maintained by [Bitbond GmbH](https://bitbond.com) (Berlin)\n\nTokenTool MCP wraps this same production infrastructure for AI agents.\n\n---\n\n## Contributing\n\n```bash\ngit clone https://github.com/thendrix-eng/token-tool-mcp\ncd token-tool-mcp\nnpm install\nnode src/index.js   # start MCP server\nnode src/cli.js     # run CLI\n```\n\nIssues and PRs welcome.\n\n---\n\n## License\n\nMIT — [Bitbond GmbH](https://bitbond.com)\n",
  "bytes": 10616,
  "sha": "3adbbb1601ee81bf64396078052d2f026678503f1f9a0ea522cd49dc4a0f379d",
  "repo_slug": "bitbond/token-tool-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_bitbond_token_tool_b89598c7/readme"
}