hw-native-sys
Related Servers
Alternatives to hw-native-sys
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables IDEs and coding agents to perform fast deterministic repository queries, symbol and dependency graph navigation, persistent memory recall, skill loading, security scanning, git inspection, and model routing with minimal token usage.MIT
- AlicenseNot gradedqualityBmaintenanceProvides semantic code intelligence tools (search, structural views) and a workspace TUI interface for LLM agents to efficiently navigate codebases, manage context, and maintain architectural patterns across Python, Java, C++, and Perl projects.4MIT
- AlicenseAqualityCmaintenanceEnables AI coding agents to retrieve cited git-history explanations for files and tickets, compile a Team Engineering Contract from repository artifacts, and follow guided Understand/Build workflows over MCP stdio. It lets clients such as Grok, Claude Code, Codex, Kiro, and Cursor share the same tools for evidence-backed repository understanding.11 npmApache 2.0
- AlicenseNot gradedqualityFmaintenanceEnables local-first codebase intelligence, allowing chat, search, and audit operations on any repository with file:line citations, and supports offline deterministic modes without an LLM.13 npm2MIT

NervusDB MCP Serverofficial
FlicenseNot gradedqualityNot gradedmaintenanceEnables building and querying code knowledge graphs for project analysis, with tools for exploring code relationships, managing workflows, and automating development tasks. Integrates with Git and GitHub for branch management and pull request creation.42 npm6-- AlicenseNot gradedqualityBmaintenanceProvides AI coding assistants with deep, semantic understanding of local codebases via AST-aware chunking, cross-repo symbol graphs, and architectural memory, enabling context-aware code search and dependency tracing.11MIT
TDQS
Scored across 37 tools
Many tools cluster around task workflows (list_tasks, list_task_types, explain_task, route_task, run_task), knowledge retrieval (search_abstractions, explain_abstraction, layer_guide, read_doc), and tracing (trace_contract, trace_in_stack), so misselection is possible. Descriptions do try to distinguish scope and light/heavy variants, but the boundaries require careful reading.
Most names use a predictable snake_case verb_noun pattern (list_repositories, search_code, explain_pass, run_task). Several noun-phrase names like repository_health, program_status, layer_guide, verify_ladder, and bootstrap_session are readable but break the strict verb_noun convention.
37 tools is well beyond typical MCP server scope and exceeds the 25+ threshold for 'too many.' The surface is broad, but many read/list/explain variants could be consolidated to reduce selection overhead.
The set broadly covers repo discovery, code search, task running, knowledge explanation, health checks, verify handoff, and session bootstrap for a compiler/hardware workflow. Minor gaps remain around write/update operations, but core read and execution paths are well represented.