Skip to main content
Glama
Vvkmnn

claude-augur-mcp

by Vvkmnn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to claude-augur-mcp

No user-submitted related servers found.

    Related Servers

    • planlimits

      rpatel021
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to inspect local Claude Code and Codex CLI usage, route tasks to the best available plan, and query remote plan data, recent changes, and recommendations.
      MIT

    • jevmem

      RyotaSanders0124
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code, Cursor, Codex, and Claude Desktop to persist decisions, rules, bugs, to-dos, and failed approaches from chats into a markdown file in the repository, then bring the relevant ones back in later sessions and flag tool calls that may break saved rules.
      236 npm
      MIT

    • Hua PlanRelay

      lmwacn
      A
      license
      A
      quality
      A
      maintenance
      Provides a workspace-safe, read-only bridge between browser-based AI planning/review and local coding agents, enabling structured plan, execution summary, and review handoffs without granting shell, file write, or Git push access.
      11
      MIT

    • Doan

      Streamize-llc
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns a rambling app idea into a structured planning canvas of screens, flows, systems, data and open questions inside an existing Claude Code or Codex session, then writes the settled plan back to that session as a spec to build from. Plans are stored in the project's .doan/ folder alongside the code.
      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.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool is exposed, so there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its purpose—extracting plan structure and returning an inline template—is clearly stated.

    Naming Consistency5/5

    The sole tool uses a clear snake_case name with a consistent augur_ prefix. With only one tool, there are no naming inconsistencies to evaluate.

    Tool Count3/5

    One tool is thin for an MCP server, but it matches a narrow, single-purpose helper. It is borderline rather than extreme because the operation is non-trivial and self-contained.

    Completeness4/5

    The tool covers the stated operation of extracting plan structure and producing a renderable template. There are no lifecycle operations like validation or template customization, but those are not clearly required by the described scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources