OpenZeppelin Contracts MCP Server

Official

Overview Schema Related Servers Score Discussions

Cairo Custom

cairo-custom

Build a custom Cairo smart contract with your chosen name, access control, pause, upgrade, and license options. Receive the generated source code as Markdown, with no file written to disk.

Instructions

Make a custom smart contract.

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.
`pausable`	No	Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
`upgradeable`	No	Whether the smart contract is upgradeable.

Schema Changelog

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

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"
+}

Changed5 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
```
First observedAug 15, 2025

TDQS

A3.8/5.0

Behavior4/5

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

The description discloses valuable behavioral traits: it returns the source code formatted in a Markdown code block and explicitly states it does not write to disk. With no annotations provided, this fills the safety/behavioral gap and clarifies the tool's non-persistent, generation-only nature. It does not elaborate on error handling or permissions, but that is acceptable for a code generation tool.

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 three short sentences with the core purpose front-loaded. Each sentence contributes essential information: the function, the return format, and the non-write behavior. There is no redundant text or filler.

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

Completeness4/5

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

Given the substantial schema coverage (83%) and the simple behavior of a code generator, the description is sufficient: it explains the core action, the output format, and that it does not write to disk. However, it lacks explicit guidance on tool selection among siblings, which would improve completeness for an agent.

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 high (83%) and the schema contains detailed descriptions for each parameter (e.g., access types, dar delays, pausable, upgradeable). The tool description adds no parameter-level information, so the baseline of 3 applies as the schema already carries the semantic weight.

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

Purpose5/5

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

The description clearly states the tool 'Make a custom smart contract' and specifies the output as source code in a Markdown code block. The tool name 'cairo-custom' together with sibling context (e.g., solidity-custom, cairo-erc20) distinguishes it as a custom Cairo contract generator, avoiding confusion with standard token or other language templates.

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 usage guidance is provided. The description does not mention when to choose this tool over the standard templates (erc20, erc721, etc.) or other custom generators (solidity-custom), and there are no preconditions, exclusions, or alternatives described.

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