hw-native-sys
Related Servers
Alternatives to hw-native-sys
No user-submitted related servers found.
Related Servers
- 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.1153 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables 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.02MIT

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.10MIT
- AlicenseAqualityAmaintenanceLocal-first code intelligence MCP server with hybrid BM25 + ONNX vector search, symbol-level impact analysis, diff-aware PR review with risk scoring, and persistent memory tied to git state.36281 npm79MIT
TDQS
Scored across 32 tools
The 32 tools overlap in several clusters, including bootstrap_session/route_task, list_knowledge_topics/list_tasks/list_task_types, explain_abstraction/explain_pass, and the multiple status/health tools. Detailed cross-references help, but an agent still faces ambiguous choices among status, listing, trace, and routing operations.
All names use lowercase snake_case consistently, with clear descriptive terms. However, the pattern mixes verb-first conventions (list_tasks, run_task, explain_pass) with noun-phrase conventions (collective_status, repository_health, bootstrap_session) rather than a strict verb_noun scheme.
32 tools is heavy for a single MCP server and exceeds the 25+ threshold where sets often become hard to navigate. The broad domain earns some of them, but the total still feels over-scoped relative to what an agent can comfortably disambiguate.
The surface covers discovery, reading, search, explanation, status, verification routing, and task execution, so most agent workflows have a path. Minor gaps remain, such as no dedicated write/update/delete operations and no direct document search, though these may be intentional for a largely read-only orchestration server.