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.

96 installs/wk local only
Foremerge
by naw103

Coordinate parallel coding agents, above Git

local only
Tirith
by eabz

Coordination server for parallel coding agents: claims, contracts, notices, and memory notes.

local only
Marrow
by aryawidjaja

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

local only
M
memento Team claims
by gitlab-memento-team-hq

Parallel coding agents claim a file before editing, so none overwrites another.

3 tools answering
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
zoanthrope
by spuentesp

Coordination relay for agent swarms: file claims, presence, postboard intentions, leases, audit.

359 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.