solidity-erc20

solidity-erc20

Generate ERC-20 standard compliant fungible token contracts with customizable features like access control, minting, pausing, and cross-chain bridging. Outputs contract source code in a Markdown format.

Instructions

Make a fungible token per the ERC-20 standard.

Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.

Input Schema

Name	Required	Description
`access`	No	The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.
`burnable`	No	Whether token holders will be able to destroy their tokens
`callback`	No	Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.
`crossChainBridging`	No	Whether to allow authorized bridge contracts to mint and burn tokens for cross-chain transfers. Options are to use custom bridges on any chain, or the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. Emphasize that these features are experimental, not audited and are subject to change. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.
`flashmint`	No	Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they're returned in the same transaction.
`info`	No	Metadata about the contract and author
`mintable`	No	Whether privileged accounts will be able to create more supply or emit more tokens
`name`	Yes	The name of the contract
`pausable`	No	Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
`permit`	No	Whether without paying gas, token holders will be able to allow third parties to transfer from their account.
`premint`	No	The number of tokens to premint for the deployer.
`premintChainId`	No	The chain ID of the network on which to premint tokens.
`symbol`	Yes	The short symbol for the token
`upgradeable`	No	Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.
`votes`	No	Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps.

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "access": {
      "anyOf": [
        {
          "enum": [
            "ownable",
            "roles"
          ],
          "type": "string"
        },
        {
          "const": "managed",
          "type": "string"
        }
      ],
      "description": "The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions."
    },
    "burnable": {
      "description": "Whether token holders will be able to destroy their tokens",
      "type": "boolean"
    },
    "callback": {
      "description": "Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.",
      "type": "boolean"
    },
    "crossChainBridging": {
      "description": "Whether to allow authorized bridge contracts to mint and burn tokens for cross-chain transfers. Options are to use custom bridges on any chain, or the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. Emphasize that these features are experimental, not audited and are subject to change. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.",
      "enum": [
        "custom",
        "superchain"
      ],
      "type": "string"
    },
    "flashmint": {
      "description": "Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they're returned in the same transaction.",
      "type": "boolean"
    },
    "info": {
      "additionalProperties": false,
      "description": "Metadata about the contract and author",
      "properties": {
        "license": {
          "description": "The license used by the contract, default is \"MIT\"",
          "type": "string"
        },
        "securityContact": {
          "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
          "type": "string"
        }
      },
      "type": "object"
    },
    "mintable": {
      "description": "Whether privileged accounts will be able to create more supply or emit more tokens",
      "type": "boolean"
    },
    "name": {
      "description": "The name of the contract",
      "type": "string"
    },
    "pausable": {
      "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
      "type": "boolean"
    },
    "permit": {
      "description": "Whether without paying gas, token holders will be able to allow third parties to transfer from their account.",
      "type": "boolean"
    },
    "premint": {
      "description": "The number of tokens to premint for the deployer.",
      "type": "string"
    },
    "premintChainId": {
      "description": "The chain ID of the network on which to premint tokens.",
      "type": "string"
    },
    "symbol": {
      "description": "The short symbol for the token",
      "type": "string"
    },
    "upgradeable": {
      "description": "Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
      "enum": [
        "transparent",
        "uups"
      ],
      "type": "string"
    },
    "votes": {
      "description": "Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps.",
      "enum": [
        "blocknumber",
        "timestamp"
      ],
      "type": "string"
    }
  },
  "required": [
    "name",
    "symbol"
  ],
  "type": "object"
}

OpenZeppelin Contracts MCP Server

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from OpenZeppelin Contracts MCP Server

Related Tools

MCP directory API