mcp-server-zig
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 | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zig_diagnosticsB | Get diagnostics (errors, warnings) for a Zig source file via ZLS |
| zig_formatA | Format Zig code using |
| zig_hoverA | Get type information and documentation for a symbol at a specific position in a Zig file via ZLS |
| zig_definitionB | Go to definition — find where a symbol is defined in a Zig codebase via ZLS |
| zig_referencesB | Find all references to a symbol at a specific position in a Zig file via ZLS |
| zig_completionsB | Get completion suggestions at a specific position in a Zig file via ZLS |
| zig_document_symbolsA | Get the document symbol outline (functions, structs, variables) of a Zig file via ZLS |
| zig_buildA | Run |
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 serves a clearly distinct purpose: building, formatting, and various LSP features like completions, definitions, diagnostics, document symbols, hover, and references. No two tools overlap in functionality.
All tools follow a consistent 'zig_<action>' pattern with snake_case, making it predictable and easy to understand the purpose from the name alone.
With 8 tools, the server covers the essential Zig development workflow (build, format, LSP features) without being bloated. The count is well-scoped for a language-specific MCP server.
The toolset covers core development tasks: building, formatting, and common LSP operations (completions, diagnostics, hover, definitions, references, document symbols). Minor gaps like renaming or code actions are absent but not critical for basic usage.