The difference between this and asking a model for an ERC20 is provenance: what comes back is OpenZeppelin's standard, parameterised, not a fresh implementation with fresh bugs. Treat the output as a starting contract — you still deploy it, and the parameters you gave (supply cap, roles, symbol) are yours to check before you do.
A contract-template server. Ask for a token or a governance contract in words and it returns Solidity built from OpenZeppelin's templates, rather than code the model wrote from memory.
- Token contracts through `get-token-contract` — ERC20, ERC721 and ERC1155, with the name, symbol and supply cap you specify
- Access control templates: role-based permissions, admin and minter roles
- Account management templates: account abstraction, multi-signature wallets, DAOs
- Finance templates: escrow, lending, pooled investment
- Governance templates: DAO governance, proposals and voting
Build from source: the project is openzipline-mcp, version 1.0.0, and the client launches `build/index.js` with node using an absolute path. Works with Claude for Desktop, Cursor and any other MCP client. No account and no key — templates are fetched from OpenZeppelin.