Skip to main content
Glama

Related Servers

Alternatives to Spaceship MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to interact with the SpaceTraders API, managing agents, fleets, contracts, and trading operations in the SpaceTraders universe.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A portable MCP server that provides a shared persistent working state for AI coding agents, managing tasks, plans, notepads, memory, and project rules across different tools like Claude Code, OpenCode, and Cursor.
      6
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server that enhances AI agents with tools for codebase analysis, task delegation to sub-agents, multi-agent coordination through chatrooms, and project todo management.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing Memoh AI agents from Claude Code, Cursor, or any MCP-compatible client, providing 26 tools for bots, containers, files, skills, memory, chat, settings, and health.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      A TypeScript MCP server for launching, tracking, and managing external coding-agent runs across local and remote backends like Codex and Claude Code. It allows top-level agents to orchestrate subagents through tools for spawning tasks, polling events, and handling interactive sessions.
      7
      2
      -

    TDQS

    A4.2/5.0

    Scored across 16 tools

    Disambiguation5/5

    All tools have clearly distinct purposes: create vs delete vs get vs list for agents, orchestrations, etc. Even similar tools like get_run_logs and get_run_status target different aspects of runs (logs vs status). test_agent and run_agent differ in synchronous vs asynchronous execution. No ambiguity.

    Naming Consistency5/5

    All tool names consistently follow the verb_noun pattern with underscores (e.g., create_agent, get_run_status, list_projects). No mixing of camelCase or other styles. Very predictable.

    Tool Count5/5

    16 tools is appropriate for a platform managing agents and orchestrations. It covers essential operations without being overwhelming. Each tool earns its place.

    Completeness4/5

    The tool set covers agent lifecycle (CRUD), run management (run, test, status, logs), orchestration operations (list, get, run, test), and listing of projects/tools. Missing delete/update for orchestrations and projects, but those may be out of scope. Minor gaps, but core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues