Skip to main content
Glama
1EchA

Context Sync MCP

by 1EchA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Context Sync MCP

No user-submitted related servers found.

    Related Servers

    • Memory Fabric

      elViRafa
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding assistants to store and retrieve project-aware context as plain Markdown files locally, with no cloud or vector database required.
      2
      MIT

    • OpenContext

      slxca
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to save and read persistent, project-local markdown context files in a .opencontext/ directory, so durable project decisions and conventions survive across sessions.
      8
      2
      11
      MIT

    • gitmem

      KuraPiee
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI coding agents persistent, branch-aware memory and a dependency-tracked task graph by storing decisions, lessons, and tasks as plain JSON and Markdown committed directly into the repository. Agents can record and fuzzy-search past decisions, dump instant project context, and create, claim, complete, and query tasks whose completion automatically unblocks downstream work.
      MIT

    • gcc-mcp

      yanhao13
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistent, structured memory for AI coding agents via a git-like filesystem with branch/commit/merge tools, enabling agents to maintain context across sessions.
      MIT

    • codebase-memory

      yuga-hashimoto
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent memory for AI coding agents through the Model Context Protocol, enabling them to store and retrieve project knowledge across sessions.
      26 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.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    The four tools split cleanly by lifecycle stage: local writing, initialization, git push, and git pull. Each description includes clear usage triggers and negative constraints, so an agent should not confuse them.

    Naming Consistency4/5

    Three tools follow a sync_<verb> pattern, while write_context uses verb_<object>. The snake_case convention is consistent and the actions are clear, so this is only a minor structural deviation.

    Tool Count5/5

    Four tools is well-scoped for a context sync server. Each tool earns its place by covering a necessary step: initialize, write, push, and load.

    Completeness4/5

    The core lifecycle from initialization to local writes to remote sync is covered, including first-time setup and new-device recovery. Minor gaps like delete operations or sync status checks are missing but are not blocking for the main workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources