syntax-map-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKSPACE_ROOT | No | The root directory of the workspace to analyze. Can be set via --workspace-root argument or WORKSPACE_ROOT environment variable. | current working directory |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_symbolsC | List top-level symbols in one supported source file. |
| find_definitionC | Find symbol definitions by name across supported source files. |
| find_referencesC | Find identifier references by name across supported source files. |
| summarize_fileC | Summarize language, line count, imports, exports, and symbols for one file. |
| run_queryC | Run a tree-sitter query against one supported source file. |
| get_ast_treeC | Return a depth-limited tree-sitter AST for one supported source file. |
| lsp_document_symbolsC | Return tree-sitter symbols converted to LSP DocumentSymbol ranges and kinds. |
| lsp_diagnosticsC | Return lightweight syntax diagnostics from tree-sitter parse errors. |
| lsp_definitionC | Return definition locations for the identifier at a zero-based LSP position. |
| lsp_referencesC | Return reference locations for the identifier at a zero-based LSP position. |
| lsp_hoverB | Return markdown hover contents for the identifier at a zero-based LSP position. |
| lsp_workspace_symbolsC | Return workspace symbols matching a case-insensitive query. |
| lsp_completionC | Return workspace symbol completion items for the prefix before a zero-based LSP position. |
| lsp_signature_helpC | Return signature help for the active call at a zero-based LSP position. |
| build_contextC | Build markdown context for supported source files. |
| index_workspaceB | Build or refresh the SQLite symbol index for all supported source files. |
| search_symbolsC | Search symbols from the SQLite workspace index. |
| find_indexed_definitionC | Find exact symbol definitions from the SQLite workspace index with snippets. |
| find_indexed_referencesC | Find identifier references from the SQLite workspace index with snippets. |
| get_index_statusB | Return SQLite index path, indexed file count, symbol count, and stale file count. |
| clear_indexB | Delete the SQLite workspace index file. |
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 21 tools
There are several overlapping triads: lsp_definition vs find_definition vs find_indexed_definition, lsp_references vs find_references vs find_indexed_references, and list_symbols vs lsp_document_symbols, plus search_symbols vs lsp_workspace_symbols. Descriptions distinguish the source and input style (LSP position, name, or SQLite index), but an agent can still easily misselect among them.
All names use snake_case and are generally readable, with consistent verb_noun patterns for most non-LSP tools. The lsp_* tools use a noun-phrase convention rather than an action verb, and a few names are longer but still predictable.
At 21 tools, the server is in the heavy borderline range, and the overlapping LSP/name/index variants inflate the surface. The count is defensible for a code-intelligence server covering tree-sitter, LSP-like actions, and SQLite indexing, but it would benefit from consolidation.
Core syntax, symbol, definition, reference, hover, completion, signature-help, diagnostics, and index lifecycle tools are present. However, common LSP/code-intelligence operations such as type definition, implementation, rename, code actions, document highlights, and workspace-wide diagnostics are missing, leaving notable gaps.