syntax-map-mcp
Related Servers
Alternatives to syntax-map-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to analyze codebases through Tree-sitter (WASM) by exposing tools for AST and symbol inspection, structural queries, reference and dependency lookup, complexity and code-similarity analysis, and project registration with directory scanning. Ships alongside a web studio with a Monaco editor, AST explorer, and read-only SQLite console.MIT
- FlicenseAqualityCmaintenanceEnables token-efficient structural code exploration using tree-sitter AST parsing, with tools for symbol search, outlines, source unfolding, call graphs, and related-file discovery.1-
- AlicenseAqualityDmaintenanceProvides code context and analysis for AI assistants by extracting directory structures and code symbols using WebAssembly Tree-sitter parsers with zero native dependencies.126 npm20MIT
- FlicenseNot gradedqualityCmaintenanceEnables full-text search for code declarations across multiple languages using SQLite FTS5 and universal ctags, allowing users to search for functions, classes, and other code elements.4-
- AlicenseNot gradedqualityCmaintenanceProvides a semantic understanding of your codebase by parsing with tree-sitter and building a graph of symbols and dependencies. Enables AI assistants to navigate code, analyze changes, and discover architecture using 18 tools with minimal context overhead.9 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables querying and analyzing code relationships by building a lightweight graph of TypeScript and Python symbols. Supports symbol lookup, reference tracking, impact analysis from diffs, and code snippet retrieval through natural language.-
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.