Skip to main content
Glama
hjamet

doc-version-mcp

by hjamet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to doc-version-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • vnsh-mcp by gaiarao

      vnsh-mcpofficial

      gaiarao
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create, read, update, and restore encrypted shared workspaces and artifacts addressed by a single link, so multiple agents and people can collaborate on the same living document. Writes are version-conditional to prevent clobbering, and content is encrypted client-side so the server only ever holds ciphertext.
      7 npm
      MIT

    • vnsh-mcp

      Robert9977
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create, read, update, list, restore, and renew client-side-encrypted shared workspaces that are reachable by a single link, so several agents and people can collaborate on the same living document with version-checked writes that refuse to clobber each other.
      7 npm
      MIT

    • vnsh

      damianparker612
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create, read, update, and share encrypted, version-controlled workspaces through a single link, so multiple agents and people can collaborate on the same living document without clobbering each other.
      7 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

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: git sync, snapshot creation, diff generation, restore, listing, and pruning. No overlapping purposes; descriptions clearly separate responsibilities.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (record_git_pull_event, commit_document, get_diff_artifact, restore_commit, list_commits, prune_commits). Verbs and nouns are clear and predictable.

    Tool Count5/5

    With 6 tools, the server is well-scoped for a document versioning domain. Each tool covers a core operation without redundancy, striking a balance between minimalism and functionality.

    Completeness5/5

    The tool surface covers the full lifecycle: create (commit_document), read/restore (restore_commit), list (list_commits), delete (prune_commits), diff (get_diff_artifact), and external integration (record_git_pull_event). No obvious gaps for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources