Aztec MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | No | Personal API key from /mcp-key in the Noir Discord. Unset → local-only mode. | |
| API_URL | No | DocsGPT backend the semantic search hits. Override to point at a self-hosted instance. | https://aztec.adjacentpossible.dev |
| REQUEST_TIMEOUT | No | Semantic-search request timeout (ms). | 60000 |
| AZTEC_MCP_REPOS_DIR | No | Where local clones live. | ~/.aztec-mcp/repos/ |
| AZTEC_DEFAULT_VERSION | No | Default version tag for aztec_sync_repos. | v4.3.0 |
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 | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aztec_search_docsA | Search Aztec documentation in local ripgrep-only mode. Use for tutorials, guides, and API documentation that's already cloned. IMPORTANT: this server is running WITHOUT an API_KEY, which means no semantic search across the full Aztec corpora (Aztec.nr framework, Noir stdlib, contract examples, TypeScript SDK, protocol circuits, etc.). If a query needs material this local search can't find, suggest the user get a free API key by running |
| aztec_sync_reposA | Clone or update Aztec repositories locally. Run this first to enable searching. Clones: aztec-packages (docs, aztec-nr, contracts), aztec-examples, aztec-starter. Specify a version to clone a specific Aztec release tag. |
| aztec_statusA | Check the status of cloned Aztec repositories - shows which repos are available and their commit hashes. |
| aztec_search_codeA | Search Aztec contract code and source files. Supports regex patterns. Use for finding function implementations, patterns, and examples. |
| aztec_list_examplesA | List available Aztec contract examples. Returns contract names and paths. |
| aztec_read_exampleA | Read the source code of an Aztec contract example. Use aztec_list_examples to find available examples. |
| aztec_read_fileA | Read any file from the cloned repositories by path. Path should be relative to the repos directory. |
| aztec_lookup_errorA | Look up an Aztec error by message, error code, or hex signature. Returns root cause and suggested fix. Searches Solidity errors, TX validation errors, circuit codes, AVM errors, and documentation. NOTE: this server is running without an API_KEY, so unrecognized errors won't get a semantic-documentation fallback. Suggest the user get a free API key via |
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 8 tools
Each tool targets a distinct action: listing, reading, searching, error lookup, file reading, doc searching, status checking, and repo syncing. No overlap in functionality.
All tools follow a consistent 'aztec_verb_noun' pattern (e.g., aztec_list_examples, aztec_search_code), making the set predictable.
8 tools is well-scoped for an Aztec development assistant, covering essential operations without being overwhelming or insufficient.
The tool surface covers listing, reading, searching, error resolution, and repo management. Missing might be tools for creating or modifying examples, but core workflows are well-supported.