Stickies

Name: Stickies
Author: dumbspacecookie

by dumbspacecookieversion 0.14.2i★ –iRuns on your computer

Registry nameio.github.dumbspacecookie/stickies

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Docs, sheets & office work
You need to fill in: STICKIES_DISCORD_WEBHOOK

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: STICKIES_DB, STICKIES_DISCORD_WEBHOOK, STICKIES_SYNC_REPO

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "stickies": {
      "command": "npx",
      "args": [
        "-y",
        "stickies-mcp"
      ],
      "env": {
        "STICKIES_DB": "your-value",
        "STICKIES_DISCORD_WEBHOOK": "your-value",
        "STICKIES_SYNC_REPO": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add stickies --env STICKIES_DB=your-value --env STICKIES_DISCORD_WEBHOOK=your-value --env STICKIES_SYNC_REPO=your-value -- npx -y stickies-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "stickies": {
      "command": "npx",
      "args": [
        "-y",
        "stickies-mcp"
      ],
      "env": {
        "STICKIES_DB": "your-value",
        "STICKIES_DISCORD_WEBHOOK": "your-value",
        "STICKIES_SYNC_REPO": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "stickies": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "stickies-mcp"
      ],
      "env": {
        "STICKIES_DB": "your-value",
        "STICKIES_DISCORD_WEBHOOK": "your-value",
        "STICKIES_SYNC_REPO": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

STICKIES_DB env
Path to the SQLite store (default ~/.stickies/stickies.db).
STICKIES_DISCORD_WEBHOOK secret env
Optional Discord webhook URL to mirror sticky lifecycle events.
STICKIES_SYNC_REPO env
Path to a git clone you own, used as the opt-in cross-machine sync store.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account dumbspacecookie, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

More stars than 0% of the other 2177 servers in this category
Published to the registry more recently than 23% of the other 2177 servers in this category
Basic checks equal to or better than 100% of the other 2177 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Stickies safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: STICKIES_DISCORD_WEBHOOK

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.14.2) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

by BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago

Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 6 days ago

Install

MCP Server for Excel

by sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 3 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

Ask Claude to remember something: *"pin a P1 todo: fix the auth leak before release."* Claude writes it down; it'll be waiting for you next session.
See your notes: type /stickies in Claude Code. Prefer a shell? npm i -g stickies-mcp gives you a stickies command — then stickies list.
Open the board in a browser: /stickies dashboard, then stickies dashboard --link for an authorized URL (the board serves your notes, so it only answers a browser you've let in).

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.

Surface	What you get	How
Terminal (Claude Code CLI)	✅ the full loop — auto-capture, session-start digest, `/stickies`, statusline, dashboard	install the plugin
Claude Desktop (chat app)	✅ read / write via MCP tools (no hooks; pass the project path)	add the MCP server to `claude_desktop_config.json`
iPhone / web (Remote Control)	✅ full loop — the phone drives a session running on your machine	run `claude remote-control` on your machine
iPhone / web (cloud sandbox)	✅ full loop via repo-mode — notes committed into the repo	`stickies init-repo` (see Repo-mode)
Any MCP client	✅ read / write	it's on the MCP Registry as `io.github.dumbspacecookie/stickies`
Anywhere, read-only	✅ a glance at your board	Discord digest / board card

Two things here you won't find elsewhere

Zero-turn capture. Claude parks a note by writing one line *in a reply it was already 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.)
Importance-graded injection. The session-start digest degrades *by importance*, not by position: P1 in full, P2 truncated, P3 a bare count. It never just chops the list at N lines.

Flow Board

If your project plans work in a .planning/ROADMAP.md (the GSD planning convention), Stickies also gives you a live Kanban board derived straight from that roadmap — To-Do / Doing / Done — with your stickies cross-linked onto the phases they're about. It's a projection of your plan, derived on the fly, so it can never drift out of sync with it.

Four places to see the same board, pick whichever fits where you are:

Where	Command	Good for
On GitHub / your phone	`stickies board` → commit `BOARD.md`	glancing at progress from a phone browser — `BOARD.md` renders natively on github.com, no server, no app
In a browser (local)	`stickies dashboard` → open `/board`	an interactive Kanban; `/graph` shows the plan's dependency DAG
In Discord	`stickies board --discord`	a push-glanceable card — progress, column counts, per-phase status
In your statusline	(see Statusline)	a tiny always-on `📋 ▶2 ☐1 ✓2` (doing / to-do / done)

stickies board                     # write BOARD.md in the project root (commit it → view on GitHub)

stickies board --out docs/BOARD.md # write it somewhere else stickies board --discord # post the board to your Discord webhook instead

Each phase shows its progress (3/4), its wave, whether it shipped (✓ shipped 4/4) and whether it's blocked (⛔). In a cloud/mobile session with no .planning/, a committed .flow/ snapshot keeps the board self-sufficient — same repo-mode idea as the notes.

Everyday commands

In Claude Code (the /stickies slash command):

Command	Does
`/stickies`	list this project's active notes (+ globals)
`/stickies all`	list every project's notes
`/stickies add`	add a note by hand
`/stickies dismiss`	clear a note (a todo is "done" when dismissed)
`/stickies dashboard`	open the local web board
`/stickies sync`	sync through your git repo (if configured)

In any shell (the CLI — same engine). Install it with npm i -g stickies-mcp to get the stickies command on your PATH, then:

stickies list                          # active notes for this dir + globals

stickies list --all # every project + globals stickies add "ship the release" -c todo -i P1 # add a P1 todo to this project stickies add "pay invoice" -c todo --due 2d # a deadline (30m/2h/1d/1w/tomorrow/YYYY-MM-DD) stickies add "call the bank" -c todo -p global # a global todo — shows up everywhere stickies dismiss -r "done" # clear it stickies dashboard --open # local web board, open the browser stickies board # write a GitHub-viewable BOARD.md stickies status # the one-line statusline summary stickies sync # pull → merge → commit (push needs STICKIES_SYNC_PUSH=1) stickies notify # push the open list to Discord stickies init-repo # make notes work in cloud/mobile (repo-mode)

Auto-capture

The lowest-friction way in: Claude captures a durable fact by writing one line in its reply, and a Stop hook persists it — no tool call, no extra turn.

!!sticky <category> [P1|P2|P3] [global] [#tag ...] :: <content>

!!sticky decision P1 #storage :: storage is node:sqlite, no native deps !!sticky todo P1 global :: cut the npm release

category is required; importance defaults to P2; notes are deduped. global and #tags are optional and may appear in any order. Without global, a note is scoped to the current project; with it, the note surfaces in every project.

The hook scans the whole completed turn, so a directive written *before* Claude runs more tools still gets saved. Directives inside subagent replies are ignored. Secrets are scrubbed on write.

Statusline

Point your Claude Code statusline at Stickies to get an always-on summary. It's opt-in — add this to your settings.json:

{ "statusLine": { "type": "command", "command": "stickies status" } }

(that uses the stickies command from npm i -g stickies-mcp)

By default it's compact — a count plus an urgency flag, e.g. 🟨 2!·19 (2 urgent of 19). It deliberately does not print note text (so nothing sensitive lands in your prompt); set STICKIES_STATUSLINE_VERBOSE=1 if you want the top note's text too.

Light / dark. A statusline can't repaint your terminal's background — it can only colour its own text — so the theme's job is to stay legible on whatever background you already have. The dark palette (default) uses the terminal's own bright colours; the light palette swaps in darker truecolour values that survive a white background (tuned to clear WCAG AA text contrast). Pick it with `STICKIES_THEME=light` (or dark) in your environment, or per-invocation with `stickies status --light` / --theme dark. On macOS/Linux terminals that publish $COLORFGBG it also autodetects; Windows Terminal / PowerShell don't set that variable, so on Windows set STICKIES_THEME explicitly if you run a light terminal. The dashboard (/, /board, /graph) is a real web page, so *it* gets a full ☾/☀ toggle that flips the whole background — that's a page it owns, unlike the statusline.

Clickable link. In a terminal that supports OSC-8 hyperlinks (Windows Terminal, iTerm2, WezTerm, Kitty, Ghostty) the segment becomes a Ctrl+click link that opens the dashboard. Two things it needs:

A dashboard must actually be running — stickies dashboard --detach. The segment is a link *only* while one is; with none running you still get the counts, just not underlined and not clickable. That is deliberate: a link to a closed port looks alive, fails only when you click it, and blames your browser rather than us. Autostart is off unless you ask for it, so no link is the default state on a fresh install. If the segment is not clickable and you expected it to be, stickies doctor says which of these two it is.
On Windows Terminal, Claude Code doesn't auto-detect hyperlink support, so set FORCE_HYPERLINK=1 in your environment *before launching Claude Code* (e.g. setx FORCE_HYPERLINK 1, then restart). Without it the segment renders but isn't clickable.

The link auto-skips under tmux (which mangles OSC-8), disables with --no-link, and its port follows STICKIES_DASHBOARD_PORT.

Dashboard

stickies dashboard                 # http://127.0.0.1:7317/

stickies dashboard --open # and open the browser stickies dashboard --detach # run in the background stickies dashboard --link # print an authorized URL for a browser stickies dashboard --stop # stop the running one

Loopback only (never leaves 127.0.0.1). Routes: / the notes board, /board the Flow Board Kanban, /graph the plan dependency DAG. One dashboard covers every project you take notes in — the header switcher moves between them, so you don't run one per folder.

It only starts when you ask. Installing Stickies does not put a server on your machine. If you'd rather each Claude session bring one up automatically, set STICKIES_DASHBOARD_AUTOSTART=1 (skipped in CI and remote sessions regardless).

"Not authorized"? That's expected, not a bug. The dashboard serves your notes and planning documents, so it answers only a browser you've authorized:

stickies dashboard --link          # → paste into your browser

…or Ctrl+click the Stickies segment in your statusline, which carries one. Opening the link sets a cookie; that's what lasts. Links themselves expire after a few minutes, so an old one from your scrollback will be refused — get a fresh one. Prefer it open? STICKIES_DASHBOARD_AUTH=0.

Editing the plan from the board is off by default. With STICKIES_BOARD_WRITEBACK=1, dragging a card rewrites that phase's **Status:** line in .planning/ROADMAP.md, keeping a pre-edit copy in .flow/roadmap-backups/. A move that contradicts the phase's plan checkboxes is refuse

Only the beginning is shown; read the rest in the repo

Stickies

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Docs, sheets & office worki

Common questions

Alternatives

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

README from the maker

Stickies (Claude Code plugin)

Quick start (60 seconds)

Where it works

Two things here you won't find elsewhere

Flow Board

Everyday commands

Auto-capture

Statusline

Dashboard