In-depth architectural comparison of the Llm Bus and Dibs MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Llm Bus
Coding Agents · Remote HTTP/SSE
Quality: 52/100 (Good) | Auth: API Key required
Dibs
Coding Agents · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Llm Bus if you need specialized Coding Agents tools running via a hosted cloud SSE transport. Choose Dibs if your workspace requires Coding Agents integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Llm Bus when:
You need dedicated capabilities in the Coding Agents domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: DATABASE_URL.
Primary tools included: Shared event ledger with exact-match queries, Attributable handoffs and read tracking, Atomic gap-free work claims.
Multi-agent coordination bus over MCP: atomic gap-free claims, advisory file leases, a shared event ledger, presence, prose handoffs, and a task graph, so multiple coding agents (Claude Code, Cursor, Codex) stop colliding and re-deriving each other's work. Remote Streamable HTTP; self-hostable (AGPL-3.0) or hosted at llm-bus.com.
Coordination layer for parallel coding agents: TTL file claims stored in the git common dir (visible across every worktree instantly), enforcement hooks that block colliding edits in Claude Code and at commit time, agent presence, handoff notes, and git-committed lessons searchable with BM25. Single static binary — no server, no database.
Category & Scope
Tools & Capabilities Breakdown
Llm Bus Tools (6)
Shared event ledger with exact-match queries
Attributable handoffs and read tracking
Atomic gap-free work claims
Advisory file leases with contention reporting
Project-scoped tasks, presence, and participant identity
Streamable HTTP MCP endpoint with bearer-token access
Dibs Tools (6)
TTL-based file and glob claims
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Llm Bus is categorized under Coding Agents and uses a remote streaming HTTP/SSE transport. In contrast, Dibs belongs to Coding Agents using local stdio subprocess. Select Llm Bus when you need capabilities focused on coding agents and Dibs when you require tools for coding agents.