OpenZeppelin Contracts MCP Server

Official

Overview Schema Related Servers Score Discussions

Cairo ERC1155

cairo-erc1155

Generates ERC-1155 token contract source with configurable access, mint, burn, pause, royalty, and URI features. Returns formatted Markdown code without writing to disk.

Instructions

Make a non-fungible token per the ERC-1155 standard.

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

Input Schema

TableJSON Schema

Name	Required	Description
`info`	No	Metadata about the contract and author
`name`	Yes	The name of the contract
`access`	No
`macros`	No	The macros to use for the contract.
`supply`	No	Whether to keep track of total supply of tokens.
`baseUri`	Yes	The location of the metadata for the token. Clients will replace any instance of {id} in this string with the tokenId.
`burnable`	No	Whether token holders will be able to destroy their tokens
`mintable`	No	Whether privileged accounts will be able to create more supply or emit more tokens
`pausable`	No	Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
`uriStorage`	No	Allows updating token URIs for individual token IDs.
`royaltyInfo`	No	Provides information for how much royalty is owed and to whom, based on a sale price. Follows ERC-2981 standard.
`upgradeable`	No	Whether the smart contract is upgradeable.
`updatableUri`	No	Whether privileged accounts will be able to set a new URI for all token types.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedv1.0.8Sep 2, 2026

addedInput schema / properties / supply

Added value: +{
+  "description": "Whether to keep track of total supply of tokens.",
+  "type": "boolean"
+}

addedInput schema / properties / uriStorage

Added value: +{
+  "description": "Allows updating token URIs for individual token IDs.",
+  "type": "boolean"
+}

Changed6 schema fields changedv1.0.1May 21, 2026

removedInput schema / properties / access / anyOf

Removed value: -[
-  {
-    "const": "ownable",
-    "type": "string"
-  },
-  {
-    "const": "roles",
-    "type": "string"
-  }
-]

removedInput schema / properties / access / description

Removed value: -"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."

addedInput schema / properties / access / properties

Added value: +{
+  "darDefaultDelayIncrease": {
+    "default": "5 days",
+    "description": "The default delay increase for the default admin role (in case Roles (Default Admin Rules) is used). Default is \"5 days\".",
+    "type": "string"
+  },
+  "darInitialDelay": {
+    "default": "1 day",
+    "description": "The initial delay for the default admin role (in case Roles (Default Admin Rules) is used). Default is \"1 day\".",
+    "type": "string"
+  },
+  "darMaxTransferDelay": {
+    "default": "30 days",
+    "description": "The maximum delay for a default admin transfer (in case Roles (Default Admin Rules) is used). Default is \"30 days\".",
+    "type": "string"
+  },
+  "type": {
+    "anyOf": [
+      {
+        "anyOf": [
+          {
+            "anyOf": [
+              {
+                "const": "ownable",
+                "type": "string"
+              },
+              {
+                "const": "roles",
+                "type": "string"
+              }
+            ]
+          },
+          {
+            "const": "roles-dar",
+            "type": "string"
+          }
+        ]
+      },
+      {
+        "const": false,
+        "type": "boolean"
+      }
+    ],
+    "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. Roles (Default Admin Rules) provides additional enforced security measures on top of standard Roles mechanism for managing the most privileged role: default admin."
+  }
+}

addedInput schema / properties / access / required
```
Added value: +[
+  "type"
+]
```
addedInput schema / properties / access / type
```
Added value: +"object"
```

addedInput schema / properties / macros

Added value: +{
+  "description": "The macros to use for the contract.",
+  "properties": {
+    "withComponents": {
+      "description": "Whether to use the \"with_components\" macro for simplified contract structure.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "withComponents"
+  ],
+  "type": "object"
+}

Changed6 schema fields changedv1.0.0Jan 3, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / access / anyOf
```
Added value: +[
+  {
+    "const": "ownable",
+    "type": "string"
+  },
+  {
+    "const": "roles",
+    "type": "string"
+  }
+]
```
- removedInput schema / properties / access / enum
```
Removed value: -[
-  "ownable",
-  "roles"
-]
```
- removedInput schema / properties / access / type
```
Removed value: -"string"
```
- removedInput schema / properties / info / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / royaltyInfo / additionalProperties
```
Removed value: -false
```
First observedAug 15, 2025

TDQS

B3.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry behavioral disclosure. It states the tool returns Markdown-formatted source code and does not write to disk, which are important side-effect facts. However, it doesn't disclose other behaviors like network calls, compilation, or whether it's purely deterministic. For a code-generation tool, the disclosed behavior is adequate but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two short sentences with no filler. It front-loads the core purpose and then states the two most operationally relevant behaviors (output format and no disk write). Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 13 parameters, nested objects, and no output schema, the description is minimal. It does not explain how to choose this tool over near-identical siblings (e.g., solidity-erc1155 or cairo-erc721), nor does it hint at what a successful response contains beyond a code block. The schema covers parameter details, but the description lacks usage context and integration guidance, making it insufficient for a tool with this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 92%, so the schema documents most parameters. The description adds no parameter-specific meaning beyond what the schema already provides. It does not explain how the numerous boolean flags interact or what the nested objects control, but the high coverage makes the schema the primary source. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it creates an ERC-1155 non-fungible token and returns source code. The verb 'Make' is specific, and the resource (ERC-1155 standard) is clear. It distinguishes from ERC-20/ERC-721 siblings, though it doesn't explicitly say this is for Cairo (relying on the tool name).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like solidity-erc1155 or cairo-erc721. There is no mention of context, prerequisites, or exclusions. The description does not help an agent decide between this and sibling code generators.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OpenZeppelin/contracts-wizard'

If you have feedback or need assistance with the MCP directory API, please join our Discord server