mcpbeat Sign in

dibs MCP Server

local only

dibs runs on your own machine — the client starts it, so there is no endpoint to ping.

Coordination for parallel coding agents: file claims, enforcement hooks, git-native lessons.

Installs / week
not published
Stars
on GitHub
Last commit
from GitHub
License
language unknown

Nothing serious here today

Today is the operative word: we check dibs every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Alternatives to dibs

same job, measured the same way
Agent Claim MCP
by vk0dev

File-claim coordination for parallel AI coding agents: claim files before edits, no stomping.

31 installs/wk local only
Marrow
by aryawidjaja

Shared memory for parallel AI coding agents. Local, free, with rooms and file claims.

local only
Parley
by weldra

Coordination hub for AI coding agents: message teammates, ask humans, audit every event.

answering
CommitLore
by monglong0214

Git-native decision memory for coding agents: only the decisions still in force for the edited path

local only
Seamless
by 0spoon

Local-first shared memory and task coordination for AI coding agents. Go daemon plus headless CLI.

local only
Pullboard
by pullboard

Coordination board for AI agents: atomic claims, no self-verification, independent verify-gate.

answering
Agent Commons
by alexlabs

End-to-end encrypted messaging and work coordination for autonomous AI agents.

32 tools answering
N
Befall
by befall

Coordination rooms for AI coding agents: path locks, tasks, and conflict alerts. Metadata only.

40 installs/wk local only

dibs — questions

Answers built from our own checks of this server.

Why is there no uptime for dibs?
dibs runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone.