MCP.Market

Stickies MCP server

by dumbspacecookie·io.github.dumbspacecookie/stickies·v0.14.2·1 stars

Persistent, expiring, importance-graded sticky notes for Claude Code.

C57/100grade C
What users say
No reviews yet
Be the first
Safety scan
C57/100

full report

Adoption
New

1 stars46 downloads/wk

Reviews

Write one

Nobody has reviewed Stickies yet.

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

Stickies tools (3, 1 write)

write = sends, deletes, buys or posts

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

  • stickies_dismiss

    Soft-delete a sticky by id (marks it dismissed; it is no longer read back).

  • stickies_read

    Retrieve active stickies relevant to the current session, ordered by importance.

  • stickies_writewrite action

    Create a persistent sticky note. Call this when a durable fact emerges

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

1 high
  • Code scan56 source files scanned13/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 qualitystatic API keys via environment variables6/15
  • Maintenancelast push 52 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10

Findings (1)

  • highShell command built from a string (injection risk)exec.shell-concat
    src/dashboard.js: …node:child_process').then(({ exec }) => exec(`${cmd} "${url}"`)); } }); …
Overall 57/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Stickies compares

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

Safety score
57/100
higher than 12% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
33%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
46
more than 38% of 12,191 servers with a package

What its tools let an agent do: 2 read · 1 change

Install Stickies in Claude Code, Cursor or VS Code

Runs npx -y stickies-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add stickies -- npx -y stickies-mcp
Add to Cursor

What the publisher says

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

Stickies (Claude Code plugin)

Persistent sticky notes for Claude Code. You pin a note — a decision, a blocker, a todo — and it survives session resets, /clear, and closing the terminal. Next time you open Claude in that project, the notes that still matter are handed back to it automatically.

Stickies is not a memory system, and it doesn't try to be one. It won't watch your session and decide what to remember. It's the opposite: a handful of notes you (or Claude, on request) write down on purpose, that expire on their own, and that you can read, prune, and trust. No vectors, no LLM summarization, no cloud. If you want an AI that auto-remembers everything, use Claude Code's built-in memory — it's on by default. Stickies is for when you want the twenty notes that actually matter, and you want them to expire.

Quick start (60 seconds)

You need Node ≥ 22.5 (node -v to check — it's for the built-in SQLite).

claude plugin marketplace add dumbspacecookie/stickies
claude plugin install stickies@stickies --scope user

Restart Claude Code. That's it — install once, it works in every project. Now try it:

Claude writes it down; it'll be waiting for you next session.

  • Ask Claude to remember something: "pin a P1 todo: fix the auth leak before release."

gives you a stickies command — then stickies list.

  • See your notes: type /stickies in Claude Code. Prefer a shell? npm i -g stickies-mcp

authorized URL (the board serves your notes, so it only answers a browser you've let in).

  • Open the board in a browser: /stickies dashboard, then stickies dashboard --link for an

Nothing leaves your machine. Everything is a local SQLite file on your disk until you turn on optional git sync.

Where it works

Notes belong to the project, not the app you're in — one local database, scoped by project. What changes between surfaces is how much happens automatically.

Two things here you won't find elsewhere

writing* — !!sticky todo P1 :: fix the auth leak — and a Stop hook persists it. No extra tool call, no extra turn, no tokens spent on a round-trip. (See Auto-capture.)

  • Zero-turn capture. Claude parks a note by writing one line *in a reply it was already

position: P1 in full, P2 truncated, P3 a bare count. It never just chops the list at N lines.

  • Importance-graded injection. The session-start digest degrades by importance, not by

Flow Board

Shortened. The full README is on GitHub.

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

Stickies: common questions

Is Stickies MCP server safe?
With care: it is graded C, so read the findings first (57/100). Read the Stickies safety report
How do I install Stickies?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Stickies need an API key?
Yes. The registry entry asks for STICKIES_DISCORD_WEBHOOK.
Is Stickies maintained?
The last commit was 93 days ago (2026-08-03). The latest release is v0.14.2.
How does Stickies compare with other MCP servers?
safety score 57/100 (higher than 12% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.