Skip to main content
Glama
icefrostiii

AgentBridge MCP

by icefrostiii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to AgentBridge MCP

No user-submitted related servers found.

    Related Servers

    • swarm-mcp

      Volpestyle
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that lets multiple coding-agent sessions on the same machine discover each other and collaborate through a shared SQLite database.
      12 npm
      1
      MIT

    • threadline-core

      richardoros
      A
      license
      A
      quality
      B
      maintenance
      MCP server providing structured continuity memory for AI coding agents, tracking decisions, open loops, and session state in local SQLite. Enables agents to resume work from verified state across sessions without replaying transcripts.
      17
      Apache 2.0

    • Claude State MCP Server

      mfitzhenry
      F
      license
      Not graded
      quality
      D
      maintenance
      SQLite-backed MCP server for Claude Code session persistence and multi-agent coordination. Provides tools for session management, event logging, decision tracking, file locking, agent registry, and plan tracking.
      -

    • MCPSaver

      cpntodd
      A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server for persistent, searchable agent memory using SQLite FTS5, replacing flat MEMORY.md files with efficient full-text search and workspace context caching.
      GPL 3.0
    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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: retrieving a task receipt, resuming a task, fetching a diff, canceling, and delegating. There is no overlap or ambiguity between these actions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_task, continue_task, get_diff, cancel_task, delegate_task) using lowercase snake_case throughout.

    Tool Count5/5

    Five tools is a well-scoped size for a task orchestration server, covering the essential lifecycle (create, read, resume, cancel, diff) without bloat or redundancy.

    Completeness4/5

    The tool set covers the full task lifecycle including creation, retrieval, resumption, cancellation, and change auditing. A minor gap is the lack of a list/query tool, but the design using handles makes it acceptable.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources