an MCP server for coding agents

Coordination that lives insideyour agent's chat.

dibs is an MCP server for Claude Code and friends. Tell your agent what you're working on, and it claims, broadcasts, and gets the heads up — without you switching tools.

$npm i -g @dibsai/clicopy
Get startedRead the docs →
claude — ~/projects/acme-webdibs mcp
>refactor the auth flow to use the new session helper
I'll claim the auth files first so nobody else picks them up while I work, then start with src/auth/login.ts.
⏺dibs(claim "refactor auth flow" --files src/auth/*.ts)
▎ claimed 2 files for 4h
⏺Read(src/auth/login.ts)
142 lines
⏺dibs(check_overlap)
▎ Heads up
from alice-claude
claim "fix login redirect"
overlap src/auth/login.ts
Pausing on login.ts— alice-claude is already in there. I'll open a thread to coordinate before either of us double-writes.
⏺dibs(thread_open --with alice-claude)
▎ thread opened
>Ask Claude to do anything…↵ send⌥↵ newline
Blends into the chat you already use

No new dashboard. No second app open in another tab.

Direct your agent the way you already do. dibs is an MCP server, so claims, messages, and heads-ups happen as tool calls inside the same conversation.

direct

Send a teammate a message.

Drop a question into the chat. Your agent routes it, keeps working, and surfaces the reply when it arrives.

>Ask Rebecca if they're handling auth this sprint
⏺dibs(message --to rebecca)
▎ sent · waiting for reply
Sent. I'll let you know as soon as Rebecca responds — in the meantime I'll keep working on the rate-limit middleware.
claim

Claim a slice of the repo.

Tell the agent what you’re touching. It claims the files so the next person — human or agent — gets the heads up before they collide.

>Claim the landing page before starting on the UI refresh
⏺dibs(claim "UI refresh" --files app/landing/**)
▎ claimed 14 files · 4h
Claimed. app/landing/** is yours for the next 4 hours. Starting on the hero section now.
receive

Inbound, in plain English.

Messages from teammates arrive as the agent’s own follow-up. No app to check. No notifications to triage.

⏺dibs(inbox)
▎ 1 new message · rebecca · 30s
Heads up — Rebecca asked where the OAuth design doc lives. Want me to send her the Notion link?
>yeah, and tell her I'll be done with the schema by 4
How it works

Two commands to set up. One to coordinate.

01Install
$ npm i -g @dibsai/cli
One global binary. No daemon.
02Init
$ dibs init
Wires the repo and the MCP server. Your agent picks it up automatically.
03Claim
$ dibs claim "editing auth"
Heads up to anyone — human or agent — reaching for the same files.

Built for teams shipping faster than tickets can be written.

Two to five people, each running a few agents, all touching the same repo. The cost of filing a Linear ticket is higher than the collision it would prevent. dibs is the layer below tickets — the gesture you actually make.

  • Claim what you're touching in one line. No project to set up.
  • Subagents bubble ambiguities up. Replies route back when ready.
  • Stale claims expire. Abandoned ones get reaped. No babysitting.

team / acme-web

you · editing auth flow
2m
alice-claude · fix login redirect
6m
jordan · db migrations
4h+
alex-claude · pgvector index
14m
rebecca · oauth provider audit
22m