Skip to main content
Glama
toxicwind
by toxicwind

Related Servers

Alternatives to identity-router

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Provides persistent identity and memory for AI agents across MCP-compatible harnesses, enabling agents to retain their name, values, and episodic memories between sessions regardless of the client or model.
      32
      11 npm
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to maintain a private, process-bound recall trail and retrieve human-reviewed, immutable knowledge editions over stdio MCP, while supporting capture, recall, feedback, and proposal creation.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to maintain a persistent identity and structured memory—including reasoning patterns, episodic history, and knowledge—while exposing procedures for managing that memory over MCP.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Provides local persistent working memory for AI agents, allowing them to load rules, preferences, and project state before tasks and save validated experiences after successful completion. Works with stdio MCP clients via a local JSON file.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent over MCP to read, file, and correct a plain-file, self-hosted personal life store — memories, people, money, body, papers, decisions and someday, alongside the usual tasks, projects, goals, habits and areas — recording every edit and deliberate non-edit so it can be reviewed and reversed. The agent does the maintenance work; the user just visits to glance at what needs them or wander through what's there.
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: current_identity reports identity state, route_lesson computes routing recommendations, and standing_files provides the ownership reference table. There is no functional overlap or plausible confusion between them.

    Naming Consistency4/5

    All names are lowercase snake_case with clear, readable words. route_lesson follows a verb_noun pattern while current_identity and standing_files are descriptive noun phrases, but the style is consistent enough that no tool name feels out of place.

    Tool Count5/5

    Three tools is well-scoped for a narrow routing/identity service: one for identity context, one for the routing decision, and one for the routing reference data. Each tool earns its place without bloat or thinness.

    Completeness5/5

    For a read-only identity-router purpose, the surface is complete: it reports the current identity, routes a lesson to the appropriate standing file, and exposes the file ownership table. There are no dead ends or obvious missing operations within its stated scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues