Sheet 1, connecting
Due Badger is a web app and an MCP server sat on the same register. Anything you can do signed in at /app, an MCP client can do on your behalf.
Add that address as a connector in your MCP client. When it asks, sign in with your Due Badger email and password. That is OAuth, and the client registers itself automatically, since Due Badger supports dynamic client registration. There is no API key to find or paste anywhere.
Restart your client once it is connected. Most MCP clients only load a server's tools when a session starts, so a freshly connected server can look broken until you do.
Sheet 2, the six tools
upcoming lists what is due soon or overdue, over a horizon you choose in days.get_obligation returns one obligation and its full history, by id or by its ref.add_obligation creates an obligation with a title and a due date, plus an
optional ref, owner, criticality, recurrence and source.complete closes an occurrence. A note is required at the tool signature, so
nothing closes without a record of what was actually done. If the obligation recurs, the
next occurrence is generated straight away.redate moves a due date. A reason is required at the tool signature, so
nothing moves without a written reason, and the original date is kept rather than lost.archive_obligation retires an obligation. It is reversible.There is deliberately no tool that deletes anything. Archiving retires an obligation without destroying it, and it can always come back.
Sheet 3, access
Every tool is scoped to the account the OAuth token was issued for. A token for one account cannot read or change another account's register.
MCP access costs nothing extra while Due Badger is free. See pricing for what that means.