MCP.Market

Docket MCP server

by pasichDev·io.github.pasichDev/docket·v3.1.0·10 stars
No reviews yet

One list every AI tool you use can write to — scoped per project, local-first, self-hostable.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

10 stars44 downloads/wk

Reviews

Write one

Nobody has reviewed Docket yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Docket tools (16, 4 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • digest_deletewrite action

    Permanently remove a digest, here and on every paired device.

  • digest_get

    One digest in full: summary, highlights, metrics, every item with its link and status, and which sources it was built from.

  • digest_list

    Recent digests, newest first, one line each. Read the latest before compiling a new one so you can say what changed since.

  • digest_publishwrite action

    Save a digest — a snapshot of the user's work across Notion, GitHub, GitLab, git and docket that YOU compiled after actually reading those sources — so it shows on the Docket dashboard and syncs to the user's paired devices. Load the docket:digest skill for how to build one. Digests are immutable: publish a new one rather than editing. Put structure in fields, not in the summary: every PR/MR/ticke

  • digest_seen

    Digest items the user marked as seen on the dashboard, with the status they had then. When compiling a digest, leave out any item whose link (or repo#ref) and status match one of these — the user has already dealt with it. An item whose status has since changed is news again: include it.

  • digest_take

    Pick up one item from a digest by its number, as the user says it: "7" or "#7" for the latest digest, "D-7K2F9A/7" for a specific one. Returns the full brief and a docket task for it — the existing one if the item already is or became a task, otherwise a new one — claimed by you. Do the work, then close it with todo_complete(id, reason); if you stop without finishing, todo_release(id).

  • todo_add

    Capture work the moment it comes up, from any tool or project, without the ceremony of a ticket. Automatically filed under the current project — you never need to say which. Add sourceUrl when it maps to something in Notion/GitLab/Obsidian/GitHub so it can be picked back up there. Use list="backlog" to park something without holding it in context; list="todo" (default) for near-term work.

  • todo_check_updatewrite action

    Check whether a newer version of docket is published on npm. Read-only — never installs anything. If one is available, tell the user and let THEM decide whether to run `docket update` in their own terminal (it asks for confirmation before installing).

  • todo_claim

    Mark an item as actively being worked on by you (the calling agent). Advisory, not a lock — check todo_list(inProgress: true) before starting new work to avoid duplicating another agent's active item. Call todo_release or todo_complete when you stop.

  • todo_complete

    Mark a todo as done by id. Pass `reason` to say how it was closed — fixed in which MR, why it was dropped — it is appended to the description and kept in history.

  • todo_deletewrite action

    Permanently remove a todo by id.

  • todo_edit

    Edit an existing item's title/description/category/priority/dueDate/sourceUrl/list by id. Only fields you pass are changed. Pass an empty string ("") for description/category/priority/dueDate/sourceUrl to clear that field.

  • todo_history

    Show the change history (create/edit/claim/release/complete) for one item, who made each change and when.

  • todo_list

    What's open here. Scoped to the current project (plus unfiled items) unless you ask otherwise, and compact by default — one line per item. Pass workspace:"*" to see every project, or verbose:true for full records.

  • todo_release

    Clear the in-progress claim on an item without completing it (e.g. you're pausing this work).

  • todo_version

    Report this docket process's data format version and start time. Use to sanity-check whether your MCP connection is running stale code (e.g. right after an update) — if todo_list output looks wrong (missing/undefined fields), check this first and reconnect if the process looks old.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • Code scan101 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 12 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Docket compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 93% of 48,243 servers
Tools
16
the typical server has 7
Tools that change things
25%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
10
more than 88% of 28,706 servers
Downloads a week
44
more than 34% of 12,306 servers with a package

What its tools let an agent do: 12 read · 4 change

Release history: 2 versions in the registry since 2026-09-05, latest 2026-10-04, typically one every 29 days.

Install Docket in Claude Code, Cursor or VS Code

Runs npx -y @pasichdev/docket on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add docket -- npx -y @pasichdev/docket
Add to Cursor

What the publisher says

From the Docket repository's README, as published. We do not edit it. Read it on GitHub

Docket

One list every AI tool you use can write to — Claude Code, Codex, Cursor, Warp — across every project, before the work is worth a ticket. Local-first, self-hostable, no SaaS account.

A thought that shows up mid-session is worth capturing but not worth the ceremony: a Notion template, a GitLab issue format, a ticket id you have to invent. So today it evaporates. Docket is the layer underneath all of that — work lands here at the speed an agent can type, from any tool, in any project, and graduates to Notion/GitLab/Obsidian when it's earned it.

Nobody else occupies this space, and it isn't an accident: Anthropic will not integrate Claude Code with Cursor, and Cursor will not integrate with Codex. Every vendor optimises its own closed loop. The space between the tools is structurally nobody's.

One list, many projects

Docket files every item under the project it was captured in, automatically — resolved from the git remote of wherever the agent is running. You never type it, and no agent has to remember to.

~/work/backend      claude-code, codex   ─┐
~/side/tracker      claude-code          ─┼──▶  docket  ──▶  one list, three scopes
~/side/notes        codex, warp          ─┘

three projects' — compact, one line each.

  • todolist in ~/work/backend shows that project's** open items, not all

guessed at.

  • The web dashboard has a workspace switcher with per-project open counts.
  • Items with no project context land under Unfiled and stay visible, never

Using the git remote rather than the path means the same repo cloned to ~/src/backend on a laptop and /work/backend on a desktop is one workspace — which matters precisely because sync exists. Full resolution order and the .docket.json override: docs/workspaces.md.

Regenerate these with node docs/assets/demo-seed.mjs — it builds the workspace they show, so they stay a picture of the real dashboard rather than a staged one.

Quick start

You need: Claude Code (or another MCP host) and Node.js 18+ (node --version; get it from nodejs.org).

npx -y @pasichdev/docket setup          # one shared data dir, detected MCP hosts configured
claude mcp add docket -- npx -y @pasichdev/docket

Restart Claude Code and ask it "add a todo: buy milk". The web dashboard is at http://localhost:8787 — it started itself the moment the first client connected.

Optionally, to see what's open in a project when a session starts:

npm install -g @pasichdev/docket        # the hook runs a command, so it needs one on PATH
docket hook install                     # then: docket hook doctor

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Docket: common questions

Is Docket MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Docket safety report
How do I install Docket?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Docket need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Docket maintained?
The last commit was 32 days ago (2026-10-04). The latest release is v3.1.0.
What can I use instead of Docket?
Servers from other publishers that do the same job: Memorix MCP server.
How does Docket compare with other MCP servers?
safety score 92/100 (higher than 93% of 48,243 servers); tools 16 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Docket

Same job from other publishers: the closest match first, then the best rated.

  • Memorix
    Local-first project memory with legacy MCP and 2026 discovery compatibility.
    B