Skip to main content
Glama
Sign In
ContextBridge

ContextBridge

by aryansingh4161-cmd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ContextBridge

No user-submitted related servers found.

    Related Servers

    • 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

    • kimi-memory

      cbuntingde
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a local-first persistent memory layer for coding assistants, enabling cross-project user preferences, per-project durable and working memory, session archives, and reflective recommendations through MCP tools.
      43 npm
      MIT

    • ContextPocket MCP Server

      JIE-Yang-618
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible coding agents to persist and retrieve durable project context—such as decisions, preferences, issues, tasks, and notes—locally across sessions without cloud services.
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool targets a fairly distinct operation: project listing/creation, knowledge write (remember), retrieval (search_memory vs get_context), live state (update_state), session snapshot (checkpoint), conflict resolution, handoff packaging, and import. The riskiest pairs are checkpoint vs prepare_handoff and remember vs update_state, but the descriptions explicitly draw those boundaries (incremental session save vs full package; decisions/rationale vs current truth). Only mild overlap remains between search_memory and get_context, both of which read project knowledge.

    Naming Consistency4/5

    Most tools follow a clean verb_noun pattern: list_projects, create_project, search_memory, update_state, resolve_conflict, get_context, prepare_handoff, import_context. Three deviate slightly — 'remember' (bare verb), 'checkpoint' (bare noun), and 'import_context' vs the noun 'memory' used elsewhere — but the set is still predictable and readable.

    Tool Count5/5

    Ten tools is well within the sweet spot and every tool maps to a real step in the project-memory lifecycle (onboard, capture, retrieve, snapshot, handoff, import). Nothing looks redundant or padded.

    Completeness4/5

    Coverage is strong: project creation/listing, knowledge capture with supersede and conflict handling, live state, checkpoints, handoff export, and staged import. The main gaps are lifecycle ends — there is no way to delete/archive a project, and no explicit 'forget/delete entry' tool (outdated knowledge can only be superseded, not removed), which an agent may occasionally need.

    Resources