Skip to main content
Glama
SettleTop-Inc

CodeRoot-Authoring-MCP

Official
by SettleTop-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CodeRoot-Authoring-MCP

No user-submitted related servers found.

    Related Servers

    • tugra

      dogrucanemek-alt
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to store and retrieve provenance-aware facts with source, age, and boundaries, supporting search, read, propose, and local telemetry via MCP tools.
      4
      491 npm
      Apache 2.0
    • CarpeOS MCP Server by innocarpe

      CarpeOS MCP Serverofficial

      innocarpe
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to capture, search, and manage structured memory from agent sessions with append-only events and provenance tracking, providing eight local MCP stdio tools.
      Apache 2.0

    • Hoplon

      justguy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents and hosts to enforce deterministic repository boundaries via MCP, providing structured reads, supervised edits, snapshots, audits, and recovery with machine-readable evidence.
      MIT

    • gitmem

      josephy02
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides MCP tools that give AI agents persistent, append-only memory in a git repository, letting them record observations, decisions, and corrections while retrieving context briefs, current facts, conflicts, and traceable event history without a vector database.
      4 npm
      MIT
    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

    A4.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: schema retrieval, fact recording, record reading, and finalization. There is no functional overlap, and the descriptions explicitly delineate boundaries (e.g., record_facts vs. finalize_record).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_, record_, read_, finalize_). The naming is predictable and unambiguous, with no mix of conventions.

    Tool Count5/5

    Four tools is an appropriate size for a focused authoring workflow. Each tool serves a necessary, non-redundant function, and the count falls well within the ideal 3-15 range.

    Completeness5/5

    The tool set covers the complete lifecycle of an asset record: reading the schema, recording facts, reading the current state, and finalizing with author confirmation. No obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources