Skip to main content
Glama

Related Servers

Alternatives to behavior-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to execute sandboxed JavaScript code to control external web applications in real-time. It utilizes WebSockets to synchronize script execution with frontend animations, allowing complex UI interactions to be handled in a single agent turn.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables personal AI agents to perceive ambient context, retain episodic memory with decay, act proactively, and route routine decisions through fast System-1 reflexes while escalating ambiguous multi-hop plans to frontier LLMs. Includes reversible execution checkpoints, token budgets, and local-first memory retention, and plugs into MCP clients like Claude Desktop, Cursor, and Windsurf.
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to combine ambient multimodal perception, continuous episodic memory, and recency-decay context briefing for fast deterministic decisions and safe tool routing. It integrates with MCP clients to reduce unnecessary frontier LLM calls while enforcing token budgets and local-first memory retention.
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to resolve typed routing, loop-stall arbitration, and tool safety checks locally at sub-millisecond latency, avoiding unnecessary frontier LLM calls. It enforces reversible execution checkpoints, token budgets, and decayed episodic memory for safe, privacy-first autonomous operation.
      7
      MIT

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct runtime concerns, but several pairs (manage_behaviors vs load_behavior, get_metrics vs get_status, abort_behavior vs register_trigger, manage_blackboard vs set_parameters) are close enough that descriptions must explicitly disambiguate them. After reading those descriptions an agent can choose correctly, so boundaries are clear but not self-evident.

    Naming Consistency5/5

    All names use a consistent snake_case verb_noun pattern: manage_behaviors, load_behavior, get_status, set_parameters, etc. The mixed verbs (manage, get, set, load, abort) are appropriate and used predictably, with no camelCase or stylistic inconsistency.

    Tool Count5/5

    Ten tools is well-scoped for a behavior runtime server covering definitions, execution, state, telemetry, triggers, recordings, and database maintenance. Each tool has a clear place and the set does not feel bloated or thin.

    Completeness4/5

    The surface covers most lifecycle needs: behavior definitions, runtime load/unload/swap, status, metrics, blackboard state, parameters, triggers, abort/pause/resume, recordings, and DB maintenance. However, replay_recording exposes only capture/list despite its name, and behavior definitions lack obvious delete/update operations, leaving minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues