bridge-mcp
Related Servers
Alternatives to bridge-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that exposes tools for issuing scoped agent credentials, delegating narrower child credentials, handling approvals, revoking task trees, and retrieving audit trails and evidence packets.141Apache 2.0
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables AI agents and teams to coordinate through shared inboxes, threaded conversations, attachments, expiring file reservations, prompts, and live notifications, while replaying missed events after restarts.443 npm2MIT
- AlicenseNot gradedqualityAmaintenanceProvides a provider-agnostic MCP server that runs structured multi-agent workflows by owning task claims, action logs, handoffs, and server-side health gates over a shared filesystem and database. It enables coordinated Explorer, Consultant, Builder, and Reviewer roles with tracked specifications and audited completion evidence.29 npmMIT
- AlicenseNot gradedqualityAmaintenanceThis MCP server provides a stateful, resettable, verifiable API runtime that gates every tool call, enabling agents to run long workflows against provider-shaped environments without live provider write access. It records decisions, side effects, and outcome evidence for replayable, verifiable benchmark runs.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables enterprise agent fleets to register workers, dispatch tasks by capability, monitor continuous heartbeat telemetry, trip automated circuit breakers, and recover from checkpointed state through a zero-dependency MCP server.MIT
- FlicenseNot gradedqualityDmaintenanceA universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.-
TDQS
Scored across 8 tools
Most tools target recognizable Bridge resources, but bridge_context_pull overlaps significantly with bridge_brief_latest, bridge_seam, bridge_decide, and bridge_scope because it pulls the same data those tools list. bridge_context is also a broad read/update tool that partially overlaps with claims and scratchpad concerns handled elsewhere.
All tools use a consistent bridge_ prefix and snake_case naming. The main deviation is bridge_context_pull, which adds a verb-like suffix while other names are primarily resource nouns.
Eight tools is a well-scoped count for a Bridge collaboration/context server. Each tool maps to a distinct area, and the surface avoids being either too thin or unwieldy.
The server covers core lifecycle operations for seams, decisions, scopes, jobs, briefs, and facts, plus aggregate context pull. Minor gaps remain around task lifecycle operations and richer brief/history retrieval, but most workflows appear supported.