base-token-factory
# Base Token Factory MCP
Deploy ERC-20 tokens on Base mainnet via the SimpleTokenFactory contract. One command, one token.
## Quick Start
Add to your `.mcp.json`:
```json
{
"mcpServers": {
"base-token-factory": {
"command": "npx",
"args": ["-y", "base-token-factory-mcp"],
"env": {
"RPC_URL": "https://mainnet.base.org",
"DEPLOYER_PRIVATE_KEY": "your-key-here"
}
}
}
}
```
`DEPLOYER_PRIVATE_KEY` is only needed for `deploy_token`. Read-only tools work without it.
## Tools
| Tool | Description |
|------|-------------|
| `deploy_token` | Deploy a new ERC-20 (name, symbol, supply, decimals, recipient). Fee: 0.0005 ETH |
| `get_deployment` | Get deployment details by ID |
| `get_deployer_tokens` | List all tokens deployed by an address |
| `get_factory_info` | Factory stats — fee, total deployed, treasury |
| `get_token_info` | Token details — name, symbol, supply, holder balance |
## Contract
- **Factory**: [`0x39D878F6c3AABFAe898ee1B2Bd5f2949784181F1`](https://basescan.org/address/0x39D878F6c3AABFAe898ee1B2Bd5f2949784181F1)
- **Chain**: Base mainnet (chainId 8453)
- **Fee**: 0.0005 ETH per deploy
## License
MIT
TDQS
Scored across 5 tools
Each tool has a distinct purpose: deploy_token creates, get_deployer_tokens lists deployments by address, get_deployment gets details by ID, get_factory_info shows contract-level info, and get_token_info returns token metadata. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (e.g., deploy_token, get_deployment), using lowercase with underscores. No mixed conventions or ambiguous verbs.
5 tools is well-scoped for a token factory server, covering creation, querying deployments, factory info, and token info. Not too many or too few for the domain.
The tool surface covers the main operations (deploy, list, get details, factory info, token info). Minor gap: no global list of all deployments, but per-deployer listing and factory total count mitigate this.