tzero-mcp
Related Servers
Alternatives to tzero-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceNext-gen AST codebase map, token compression (70%~85% savings), and context packaging engine for AI coding agents & IDEs.43MIT
- AlicenseAqualityDmaintenanceProvides intelligent code context and analysis through semantic compression, AST parsing, and multi-language support. Offers 60-80% token reduction while enabling AI assistants to understand codebases through local analysis, OpenAI-enhanced insights, and GitHub repository integration.617 npm3MIT
- AlicenseBqualityBmaintenanceEnables LLMs to efficiently read, write, and refactor code using precise AST-based operations, reducing token usage and context window waste.25110 npm3MIT
- AlicenseNot gradedqualityCmaintenanceProvides structured, token-efficient code context for AI assistants by indexing codebases with AST-level analysis, supporting 17+ languages, enabling semantic search, call-site tracking, and PR attribution.77 PyPI40MIT
- AlicenseNot gradedqualityDmaintenanceMake any LLM a codebase expert instantly. Provides deep code intelligence through semantic search, architecture mapping, security analysis, and smart context that fits perfectly in token windows.MIT
- FlicenseAqualityBmaintenanceEnables precise source code retrieval via tree-sitter AST parsing, cutting AI token costs by 86-99% by indexing codebases and fetching only needed symbols and structural queries (e.g., blast radius, importers) on demand.61-
TDQS
Scored across 15 tools
Most tools pair a distinct resource with a distinct action, and descriptions explicitly cross-reference siblings to draw boundaries (e.g. enforce vs. manage architecture rules). However, 'execute_codebase_workflow' explicitly re-implements every other tool's action (audit, security, blueprint, dependencies, search, prune, heal, memory, swarm), and 'build_project_context' (tree mode) heavily overlaps with 'generate_architecture_blueprint' and 'analyze_code_dependencies'. This creates real misselection risk: an agent can reasonably pick either the master tool or the specialist for the same task.
All 15 names are snake_case verb_noun pairs (enforce_, analyze_, search_, estimate_, generate_, audit_, verify_, manage_, build_, prune_, query_, orchestrate_, execute_). No camelCase, casing, or stylistic outliers; the pattern is highly predictable.
15 tools sits at the top of the well-scoped 3-15 band and the broad domain (architecture, quality, security, context, search, memory, orchestration) justifies most of them. The master 'execute_codebase_workflow' tool and the swarm orchestrator are arguably redundant scope creep on top of an already complete surface.
Coverage is broad for a local code-intelligence toolkit: search, context building, snippet pruning, dependency/impact analysis, quality audit, secret scanning, architecture rule lifecycle plus enforcement, and blueprint generation. Minor gaps exist around applying fixes or running tests (orchestrate_agent_swarm only patches via 'self_healing'), leaving some workflows as dead ends, but core read-only analysis is fully covered.