agentmako
Related Servers
Alternatives to agentmako
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceLocal-first codebase context engine that parses code into a ranked dependency graph and serves it to AI tools via MCP for deep structural understanding.518 npm1MIT
- AlicenseNot gradedqualityCmaintenanceA local-first codebase intelligence layer for AI coding agents, providing a persistent, queryable model of a repository via an MCP server and CLI to enable structure queries instead of reading many files.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceLocal-first code intelligence MCP server that enables coding agents to search code, inspect structure, read exact ranges, and explore Git history with explicit token budgets.33Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally search, query, and understand codebases with token-efficient context, dependency graphs, history, architecture diagrams, and metrics through MCP.15 npm3MIT
- FlicenseNot gradedqualityAmaintenanceProvides a local-first code indexing and search engine for coding agents via MCP, enabling precise codebase queries, symbol lookup, and freshness-aware retrieval.-
- AlicenseNot gradedqualityAmaintenanceLocal repository intelligence MCP server that builds a reusable graph of code structure for AI coding agents, providing 34 network-free tools for understanding, searching, and analyzing repositories without data leaving the machine.58 npmMIT
TDQS
Scored across 105 tools
With 105 tools, several are near-duplicates: reef_status and reef_agent_status describe essentially the same status report, and reef_impact is explicitly an equivalent of reef_diff_impact. Large clusters around status, verification, diagnostics, and querying blur boundaries, so an agent will frequently struggle to pick the right tool.
Most names are readable snake_case with useful prefixes like trace_*, db_*, and file_*, but the conventions are mixed: verb_noun (trace_table), noun_noun (schema_usage), and bare verbs (ask, suggest, investigate) all appear. The inconsistent word order and singular/plural choices across families prevent a fully predictable pattern.
105 tools is an extreme count for any MCP server, far beyond the 50+ threshold for a 1. The breadth does not justify the size because many tools are near-duplicates or slight variants rather than distinct capabilities.
Coverage is broad across code search, tracing, database inspection, diagnostics, findings, and session recall, but there is no simple file read tool despite full file mutation tools, and the four artifact composers have no artifact read/list counterpart. Shell_run and live_text_search can work around some gaps, but the lifecycle is not complete.