skel-mcp
Related Servers
Alternatives to skel-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and IDEs to query a local structural code graph and retrieve focused, token-bounded context on code entities, Git relationships, callers/callees, impact, paths, and recorded mistakes for more efficient sessions.24 npmMIT
- AlicenseAqualityBmaintenanceEnables coding agents to query compiler-grade code intelligence—such as references, definitions, implementations, and impact analysis—returning code snippets instead of file locations.11MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to retrieve bounded, focused context from a local structural code graph, including source entities, Git relationships, and recorded project memory. It supports exploring structure, inspecting callers, callees, and impact, and carrying prior mistakes into later sessions without reading full files.24 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to query a codebase as a graph, retrieving definitions, callers, callees, dependencies, and focused context so they fetch only the code they need instead of reading whole repositories.MIT

Graphicle MCP Serverofficial
AlicenseBqualityAmaintenanceEnables coding agents to query a repository's code graph and project memory through cited excerpts, navigate symbols and dependencies, and optionally inspect pull requests, all within a configurable token budget.22571Apache 2.0- FlicenseAqualityDmaintenanceProvides codebase indexing and retrieval tools that give AI agents token-efficient, query-relevant context packages (symbols, imports, and dependencies) instead of scanning entire repositories.6-
TDQS
Scored across 1 tool
Only one tool exists, so there is no inter-tool ambiguity to speak of. However, get_context internally multiplexes four distinct modes (outline, symbol, lines, diff) plus cursor/token options, which places the disambiguation burden on the description rather than the tool surface.
A single verb_noun name (get_context) is inherently consistent and clearly signals a read operation. No naming conflicts or mixed conventions are possible with one tool.
One tool for the whole server is thin, even though it is a multi-mode mega-tool that internally covers several read operations. It is borderline: workable for read-only AST context, but it concentrates all capability into a single overloaded entry point.
Read coverage looks solid for the domain (outline, symbol body, literal line matching, diff, pagination), but there are no write operations and no non-literal/regex or symbol-name search mode. Agents can work around this but some retrieval intents will be awkward.