Skip to main content
Glama
GDM-Pixel

Stellaris MCP

by GDM-Pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Stellaris MCP

No user-submitted related servers found.

    Related Servers

    • Serena MCP Server

      Raheem-19
      A
      license
      B
      quality
      D
      maintenance
      Provides IDE-like semantic code retrieval and editing tools for LLMs, enabling precise code understanding and manipulation in large codebases via the Model Context Protocol.
      25
      MIT
    • CodeAlive MCP by CodeAlive-AI

      CodeAlive MCPofficial

      CodeAlive-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      A 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.
      90
      MIT

    • astra-mcp

      nimelkot
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to index local Python repositories and retrieve code intelligence through semantic search, caller lookups, hybrid context expansion, and visualization.
      5
      MIT

    • mcp-codebase-index

      MikeRecognex
      A
      license
      Not graded
      quality
      D
      maintenance
      A structural codebase indexer that exposes 18 tools via the Model Context Protocol for AI-assisted code navigation, enabling efficient querying of functions, classes, dependencies, and call chains without reading entire files.
      87 PyPI
      62
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 30 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources