Stellaris MCP
Related Servers
Alternatives to Stellaris MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides IDE-like semantic code retrieval and editing tools for LLMs, enabling precise code understanding and manipulation in large codebases via the Model Context Protocol.25MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to semantically navigate codebases via an AST index, supporting symbol search, usage lookup, module exploration, and dependency analysis.MIT

CodeAlive MCPofficial
AlicenseNot gradedqualityAmaintenanceA Model Context Protocol server that enhances AI agents by providing deep semantic understanding of codebases, enabling more intelligent interactions through advanced code search and contextual awareness.90MIT- 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
- AlicenseBqualityBmaintenanceEnables AI agents to index local Python repositories and retrieve code intelligence through semantic search, caller lookups, hybrid context expansion, and visualization.5MIT
- AlicenseNot gradedqualityDmaintenanceProvides semantic codebase understanding via a graph, enabling AI agents to search, explore, and plan changes with whole-repo context in a single tool call.31MIT
TDQS
Scored across 30 tools
Each tool has a clear, distinct purpose with no overlaps. Dependency analysis tools (get_dependencies, get_dependents, get_most_coupled, etc.) are precisely differentiated, and the token-efficient exploration sequence (search_code -> get_file_outline -> get_file_folded -> get_symbol) is well-structured. Even closely related tools like db_schema and db_search serve different functions.
Most tools follow a verb_noun pattern with snake_case (e.g., get_dependencies, search_code). However, the verb choices vary (get, search, detect, find, simulate) and some names are compound (detect_significant_changes) or use adjectives (get_most_coupled), resulting in minor inconsistency.
With 30 tools, the server significantly exceeds the typical well-scoped range of 3-15. While each tool is justified, the set spans multiple domains (code analysis, database, usage monitoring) that could be split into separate servers. This large surface area may overwhelm agents.
The tool set comprehensively covers code analysis, dependency management, project health, documentation search, database introspection, and usage tracking. All essential operations for these domains are present, with no obvious gaps in the workflow.