solidity-erc721

solidity-erc721

Generate ERC-721 compliant non-fungible token contracts with customizable features like access control, voting, and upgradeability. Outputs source code in Markdown without saving to disk.

Instructions

Make a non-fungible token per the ERC-721 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.
`baseUri`	No	A base uri for the token
`burnable`	No	Whether token holders will be able to destroy their tokens
`enumerable`	No	Whether to allow on-chain enumeration of all tokens or those owned by an account. Increases gas cost of transfers.
`incremental`	No	Whether new tokens will be automatically assigned an incremental id
`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.
`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.
`uriStorage`	No	Allows updating token URIs for individual token IDs
`votes`	No	Whether to keep track of individual units for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps (defaulting to block number if not specified).

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."
    },
    "baseUri": {
      "description": "A base uri for the token",
      "type": "string"
    },
    "burnable": {
      "description": "Whether token holders will be able to destroy their tokens",
      "type": "boolean"
    },
    "enumerable": {
      "description": "Whether to allow on-chain enumeration of all tokens or those owned by an account. Increases gas cost of transfers.",
      "type": "boolean"
    },
    "incremental": {
      "description": "Whether new tokens will be automatically assigned an incremental id",
      "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"
    },
    "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"
    },
    "uriStorage": {
      "description": "Allows updating token URIs for individual token IDs",
      "type": "boolean"
    },
    "votes": {
      "description": "Whether to keep track of individual units for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps (defaulting to block number if not specified).",
      "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