Skip to main content
Glama
muhammadluth

Runar

by muhammadluth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Runar

No user-submitted related servers found.

    Related Servers

    • codemem

      jeang42
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, searchable memory across coding projects and machines, letting agents record and retrieve projects, reusable assets, sessions, decisions, commits, and handoffs via MCP.
      2
      Apache 2.0

    • MCP Shared Memory Hub

      shirisha456
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple MCP-compatible AI clients to share persistent, versioned project knowledge across sessions with conflict-safe updates, provenance, hybrid retrieval, stale-memory handling, and context-budgeted recall.
      MIT

    • Jatobá Brain

      Ey-luccas
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent, multi-project memory for AI agents via MCP, enabling them to store and retrieve tasks, decisions, errors, checkpoints, and documentation while keeping context isolated by project.
      2
      MIT
    • Qoopia by qoopia

      Qoopiaofficial

      qoopia
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent memory for AI agents via MCP, enabling agents to store and access notes, files, and session context across sessions and clients while under user control.
      1
      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

    B3.2/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool is scoped to a distinct resource namespace and action, so memory, session, skill, persona, and context operations are easy to separate. The only conceptually adjacent pair, memory.search and context.build, is clearly distinguished by 'find candidates' versus 'build pack'.

    Naming Consistency5/5

    All tools follow a consistent lowercase namespace.action convention with predictable verbs like list, get, validate, enable, disable, read, and write. There is no mixing of separator styles or naming patterns, so agents can infer related tools across resource types.

    Tool Count5/5

    Fifteen tools is at the upper edge of the ideal range, but each tool maps to a necessary operation across the server's five related domains. There is no obvious redundancy or dead weight in the set.

    Completeness4/5

    Core workflows are covered: memories can be proposed, read, searched, archived, and analyzed; skills can be listed, inspected, validated, and toggled; sessions and contexts have write/build paths. Minor gaps exist—such as no direct memory update or persona activation tool—but archive-and-repropose and resource URI patterns provide reasonable workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources