OpenZeppelin Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| oz_index_statusA | Check if the OpenZeppelin docs index is ready. Call this if other tools report the index is building. |
| search_oz_docsC | Search OpenZeppelin Contracts documentation for guides, API references, and code examples |
| get_oz_contractC | Get detailed API reference for a specific OpenZeppelin contract or library |
| get_oz_functionC | Get detailed information about a specific function in OpenZeppelin Contracts |
| list_oz_modulesB | List all available OpenZeppelin contracts and libraries, optionally filtered by category |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: get_oz_contract retrieves contract-level details, get_oz_function focuses on specific functions, list_oz_modules provides a catalog, oz_index_status checks system readiness, and search_oz_docs performs general documentation searches. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent snake_case naming pattern with clear verb_noun structures: get_oz_contract, get_oz_function, list_oz_modules, oz_index_status, and search_oz_docs. The 'oz' prefix is uniformly applied, and verbs like 'get', 'list', and 'search' accurately describe the actions, ensuring predictability across the set.
With 5 tools, this server is well-scoped for its purpose of accessing OpenZeppelin documentation. Each tool serves a distinct and necessary function, from indexing and searching to retrieving specific details, without being overly sparse or bloated, making it efficient for agents to navigate.
The tool set covers core documentation needs comprehensively, including listing, searching, and retrieving detailed information at both contract and function levels, with a status check for system readiness. A minor gap might be the lack of tools for updating or managing documentation, but this is reasonable for a read-only documentation server, and agents can perform all essential queries without dead ends.