Skip to main content
Glama
baalimago

slivingdoc

by baalimago
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Related Servers

Alternatives to slivingdoc

No user-submitted related servers found.

    Related Servers

    • memory-mcp

      credp
      A
      license
      B
      quality
      A
      maintenance
      A local MCP server that provides agents with tools to list, read, search, inspect history and diffs, and capture unstructured text in a user-owned Git repository of durable memory.
      5
      MIT

    • Git MCP Server

      a-g-e-n-t-s
      A
      license
      Not graded
      quality
      D
      maintenance
      A secure and scalable Git MCP server giving AI agents powerful version control for local and (soon) serverless environments.
      47 npm
      Apache 2.0

    • Cellar

      fbereilh
      A
      license
      Not graded
      quality
      A
      maintenance
      An interactive notebook server that enables humans and AI agents to collaboratively edit and run Jupyter notebooks on a shared kernel, with real-time streaming and automatic MCP integration for agent access.
      18 npm
      MIT

    • git-courer

      blak0p
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives AI agents a full, safe interface to Git with automatic backups, isolated worktrees, and structured JSON outputs.
      44
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    notes_commit and notes_pull have clearly distinct purposes: one publishes local changes and incorporates concurrent changes, the other writes the current notebook into the directory. Their descriptions make the boundary unambiguous.

    Naming Consistency5/5

    Both tools follow a consistent notes_<verb> snake_case pattern. There are no deviations or mixed conventions.

    Tool Count3/5

    With only two tools, the set is borderline thin for a notebook version control system. While each tool earns its place, typical workflows require more operations.

    Completeness2/5

    The toolset covers only pull and commit, missing critical operations such as conflict resolution, status, history, and initialization. These significant gaps will cause agent failures in realistic use.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources