Skip to main content
Glama
leo7nel23

RBT Document Editor

by leo7nel23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to RBT Document Editor

No user-submitted related servers found.

    Related Servers

    • mcp-code-context

      achatainga
      A
      license
      B
      quality
      B
      maintenance
      Enables LLMs to efficiently read, write, and refactor code using precise AST-based operations, reducing token usage and context window waste.
      25
      19 npm
      3
      MIT

    • Semantic Cache MCP

      CoderDayton
      A
      license
      A
      quality
      A
      maintenance
      Reduces token consumption by over 80% through intelligent file caching, returning only diffs for modified files and suppressing unchanged content. It features a suite of 12 tools for semantic search, batch reading, and efficient file editing to optimize LLM interactions with large codebases.
      14
      2
      MIT

    • doc-agent-mcp

      xyyyang97
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to perform safe, semantic edits on Markdown and DOCX documents through a normalized model with staging, diff review, and stale-edit protection.
      13
      MIT

    • mcp-text-editor

      tumf
      A
      license
      A
      quality
      A
      maintenance
      A line-oriented text file editor. Optimized for LLM tools with efficient partial file access to minimize token usage.
      6
      200
      MIT

    • mcp-fstools

      devrandom
      F
      license
      A
      quality
      B
      maintenance
      Provides file read, edit, and write operations with exact-match editing and hash-based consistency checks, designed for models that prefer structured schemas over patch grammars.
      3
      -
    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.5/5.0

    Scored across 8 tools

    Disambiguation3/5

    The tools have some clear distinctions (add_document vs. search operations), but there is notable overlap between delete_entity_edge and delete_episode (both delete operations on graph components) and between search_memory_facts and search_memory_nodes (both search operations with similar parameters). The descriptions help differentiate them, but an agent might occasionally misselect between these pairs.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern (e.g., add_document, clear_graph, delete_entity_edge, get_episodes, search_memory_facts). The naming is uniform across all eight tools, using snake_case throughout without any deviations or mixed conventions.

    Tool Count4/5

    With 8 tools, the count is reasonable for a document editor and graph memory management system. It covers core operations like adding documents, clearing data, deleting entities, retrieving information, and searching. However, it feels slightly thin for a full CRUD lifecycle, as there are no update tools for entities or episodes, but the scope is still well-defined.

    Completeness3/5

    The toolset covers key operations for document syncing and graph memory management, including add, delete, get, and search functions. However, there are notable gaps: no update tools for entities or episodes, and no create tools for entities or episodes independently (only via add_document). This could lead to dead ends when agents need to modify existing graph data without replacing entire documents.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources