Skip to main content
Glama
Sign In
MiuDog

planist-mcp

by MiuDog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to planist-mcp

No user-submitted related servers found.

    Related Servers

    • Bludit Wizard MCP

      gitdamnit
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI clients to discover, read, search, draft, and edit pages on a locally owned Bludit CMS site, with human-controlled approval and revision checks before changes are applied.
      GPL 3.0

    • agent-workflow

      GallonShih
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude Desktop, Claude Code, and Cursor to discover node types, author and validate typed multi-agent workflow files, launch runs against a workspace, and retrieve run status, node outputs, and workspace change details.
      MIT
    • Splendorize MCP Server by splendorize

      Splendorize MCP Serverofficial

      splendorize
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects MCP-compatible AI clients to landing-page intelligence, evidence packs, improvement suggestions, experiment drafting and review, preview scans, instrumentation validation, site configuration, and integrations. Customer-facing writes require explicit OAuth scopes and confirmation.
      MIT
    • Planwright by soundheart-studios

      Planwrightofficial

      soundheart-studios
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents and humans to collaborate on local, evidence-driven planning by exposing MCP tools for plan listing and binding, workflow catalog/run operations, and task tracking with human-reviewed decisions.
      2
      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 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation on either pages or variables: list/read/propose for pages, and list/get/update for variables. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the consistent planist_<verb>_<noun> pattern using snake_case. Verbs are clear and specific (list, read, get, propose, update), making the naming predictable and coherent.

    Tool Count5/5

    With six tools, the server is well-scoped for managing pages and variables. The count is within the ideal 3-15 range and each tool serves a clear purpose without unnecessary bloat.

    Completeness3/5

    The server covers read, list, and update operations for both pages and variables, but lacks any creation or deletion capabilities. This is a notable gap in the resource lifecycle, though the propose-edit workflow adds a distinct review step for page modifications.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources