clangd-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | MCP log level (ERROR/WARN/INFO/DEBUG) | INFO |
| CLANGD_ARGS | No | Additional clangd arguments | Auto-configured |
| CLANGD_PATH | No | Path to clangd binary | Auto-detected |
| PROJECT_ROOT | No | Project workspace root | Current directory |
| CLANGD_LOG_LEVEL | No | Clangd log level | error |
| COMPILE_COMMANDS_DIR | No | Path to compile_commands.json directory | Auto-detected |
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 |
|---|---|
| find_definitionB | Find the definition of a symbol at a given location in a file |
| find_referencesB | Find all references to a symbol at a given location |
| get_hoverA | Get hover information (type, documentation) for a symbol at a given location |
| workspace_symbol_searchC | Search for symbols across the entire workspace |
| find_implementationsB | Find implementations of an interface or virtual method at a given location |
| get_document_symbolsC | Get a hierarchical list of all symbols in a document |
| get_diagnosticsB | Get diagnostics (errors, warnings, notes) for a file |
| get_call_hierarchyC | Get call hierarchy showing incoming callers and outgoing callees for a function |
| get_type_hierarchyB | Get type hierarchy showing base classes (supertypes) and derived classes (subtypes) |
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 9 tools
Each tool serves a distinct code analysis purpose such as finding definitions, references, or diagnostics; there is no functional overlap.
All tool names follow a consistent verb_noun pattern (e.g., find_definition, get_diagnostics) using snake_case, making them predictable.
9 tools are well-scoped for a code intelligence server, covering the essential operations without being excessive.
The tool surface covers core navigation and inspection needs; minor gaps like rename or code completion are absent but not critical for the server's purpose.