get-token-contractLABSCO SUMMARY
The value is that the model did not write the contract.
An LLM asked for an ERC20 will produce something that compiles and may not be safe. Fetching the OpenZeppelin template instead means the security properties come from a library that has been audited, and the model's job shrinks to filling in the name, symbol and cap. Treat the output as a starting point rather than a deployment: the moment you edit the template, the provenance argument stops applying to your version.
What it is
An MCP server that fetches and generates smart contract templates from OpenZeppelin, so an assistant can hand back Solidity for a named token or governance pattern rather than writing it from memory. The point is provenance: the contract comes from the audited library, not from the model.
What you get
- ERC20, ERC721 and ERC1155 contracts generated with the name, symbol and supply cap you asked for —
get-token-contractis the tool the client picks for these - Access control templates for role-based permissions, including admin and minter roles
- Account management templates: account abstraction, multi-signature wallets and DAO structures
- Finance templates: escrow, lending and pooled investment contracts
- Governance templates for DAO proposals and voting, including token-based voting
Requirements
Nothing external — no account, no key, no wallet. There is no published package: build from a clone and point your client at build/index.js by absolute path, in Claude Desktop's config or Cursor's MCP servers file, then restart the client. What it returns is a template — deployment, constructor arguments and any audit of your modifications are still yours.
Setup effort
Build from source — git clone https://github.com/codewithdpk/openzippelin-mcp.git
USE CASES
01
Bootstrapping a token contract
Describe the token — name, symbol, supply cap — and get the matching standard's template back filled in.
02
Starting an NFT project
Ask for an ERC721 for the collection, or ERC1155 when a game or platform needs multiple item types in one contract.
03
Adding role-based permissions
Request the access control template with the roles you need, rather than hand-rolling a permission modifier.
04
Setting up DAO governance
Ask for the governance template covering proposals and voting, then adapt it to your token.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/codewithdpk/openzippelin-mcp.git
cd openzippelin-mcp
npm install
npm run buildMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"openzippelin-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PARENT_FOLDER>/openzippelin-mcp/build/index.js"
]
}
}
}
