Skip to main content
Glama
IMAFDI

polyplan-mcp

by IMAFDI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to polyplan-mcp

No user-submitted related servers found.

    Related Servers

    • Zen MCP Server

      salvadorthebrown
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Orchestrates multiple AI models (Gemini, OpenAI, Claude, local models) within a single conversation context, enabling collaborative workflows like multi-model code reviews, consensus building, and CLI-to-CLI bridging for specialized tasks.
      -

    • all-agents-mcp

      Dokkabei97
      A
      license
      B
      quality
      F
      maintenance
      Enables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.
      14
      17 npm
      14
      MIT

    • cross-agent

      WSH95
      A
      license
      B
      quality
      B
      maintenance
      Runs headless claude, codex and grok processes as one team from whichever of the three CLIs you work in, letting your session delegate work to other engines in their own sandboxes with modes that assign planner, reviewer, implementer and resolver roles and enforce git merge guards.
      13
      MIT

    • Agent Squad Bridge

      kagtgi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI coding CLIs (Claude Code, Gemini/Antigravity, Codex, and OpenCode) to collaborate as a coordinated team by routing cross-agent prompts, sharing messages and review tickets, tracking tasks on a shared store, and isolating each agent in its own Git worktree with turn-budget safeguards—all inspectable and steerable from a local web dashboard.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, covering specific actions like initialization, round management, context retrieval, and status queries. No two tools overlap in functionality, and descriptions make their roles unambiguous.

    Naming Consistency4/5

    Tool names mostly follow predictable patterns: verbs for actions (clear, export, init), 'show_' for queries, and 'round_' nouns for round commands. The 'context' suffix for context tools and 'round_1' vs 'round_1_context' is consistent, though a few names (e.g., 'final_plan') mix noun phrases with actions.

    Tool Count5/5

    16 tools is well-scoped for a planning session orchestrator covering init, two rounds, final synthesis, and full state queries. Each tool earns its place with no redundancy.

    Completeness5/5

    The tool set fully covers the planning lifecycle: initialization, round creation with context, final plan synthesis, status display, conflict/agreement analysis, history, and export. No obvious gaps like per-model plan deletion or editing are missing for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources