Sticky

io.github.1picassoaiPublished by GitHub account 1picassoaiv0.2.2Updated Oct 24, 2026

Persistent memory and context for your agent, on a board you can see. Capped, so it stays small.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A local MCP server that gives a coding agent a small, capped sticky-note board for persistent memory, viewable and editable in a browser.

What you can do
Post notes to a board to pin decisions, constraints, or where work paused, and read the active board at the start of a session, so context carries across sessions without a growing rules file. Notes live in three columns: Pinned permanent rules, Active current decisions (newest ten reach the agent), and an Archive that never reaches the model. The board opens in a browser and updates live as the agent posts; notes can be dragged between columns, edited, or deleted. Active is capped at 10 (configurable 5–20) and Pinned at 15, keeping the agent's context bounded at roughly 25 notes.
When to use it
Useful when a coding agent forgets context between sessions and you want a small, visible, self-pruning memory instead of an ever-growing instruction file. Suits developers who want to watch and curate what the agent remembers, and who prefer local-only storage.
Requirements
Runs locally via npx (npm package sticky-mcp) over stdio; requires Node 22.5 or newer, which provides built-in SQLite. No account, cloud, API key, or configuration. The board is a SQLite file at ~/.sticky/store.db, and its web server binds to 127.0.0.1 on port 7317 by default.
Before you install
The agent can write notes that persist and shape later sessions, so review the board and retire stale or wrong rules. Pinned rules always reach the agent and the board refuses a sixteenth, so pinned content needs occasional pruning. Notes are stored locally in a SQLite file; the README states there is no telemetry or network code beyond the local server.

Installation

In SourceWeft

  1. Open Sticky in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

STICKY

[image]

A board your coding agent can write to — and you can see.

Your agent forgets between sessions. The usual fix is a CLAUDE.md that grows until it's a thousand lines of stale rules nobody deletes, quietly costing you tokens on every request.

STICKY holds ten active notes. When the eleventh arrives, the oldest one tumbles to the archive on its own. Nothing to prune, nothing to garden.

bash
npx sticky-mcp

That's it. The board opens in your browser. No account, no cloud, no config.

Wire it to your agent

bash
claude mcp add sticky -- npx sticky-mcp-server

Cursor, Cline, Windsurf and anything else that speaks MCP work the same way — point them at npx sticky-mcp-server.

Or add it to your MCP config by hand:

json
{  "mcpServers": {    "sticky": {      "command": "npx",      "args": ["-y", "sticky-mcp-server"]    }  }}

sticky-mcp-server takes no flags on purpose. Some CLIs — Claude Code among them — read -y and --mcp as their own options and never pass them through, so a command with nothing after it is the only one that works everywhere.

Your agent gets two tools:

  • post_sticky — pin a decision, a constraint, or where the work paused
  • read_active_stickies — read the board at the start of a session

The three columns

what it holdsreaches the agent
Pinnedpermanent rules — "use C# 12", "never touch migrations by hand"always
Activecurrent decisions and where work stoppedalways, newest 10
Archivewhatever tumbled offnever — zero tokens

Drag a note between columns. Drop it on Pinned and it becomes a permanent rule. Drop it on Archive and it stops reaching the agent immediately. Double-click to edit, click the cross to bin a bad assumption.

The board updates live as your agent posts — you watch it think.

What's bounded, and what isn't

Being precise, because a promise that isn't quite true is worse than no promise:

  • Active is capped at 10 (configurable 5–20). The oldest unpinned note tumbles out.
  • Pinned is capped at 15. Rules never tumble — a rule vanishing silently would be worse than the bloat — so instead the board refuses the sixteenth and asks you to retire one.
  • Archive is unbounded and costs nothing, because it never reaches the model.

So the agent's context stays bounded at roughly 25 notes, permanently, no matter how long you work.

Your data

The board is a SQLite file at ~/.sticky/store.db. The web server binds to 127.0.0.1 and nothing else. There is no telemetry, no analytics, and no network code in this package beyond the local server itself.

Options

npx sticky-mcp                 open the boardnpx sticky-mcp --mcp           run as an MCP server (agents launch this)
  --cap <n>      active notes before the oldest tumbles (default 10)  --port <n>     board port (default 7317)  --db <path>    where the board lives (default ~/.sticky/store.db)  --no-open      start without opening a browser

Want it floating beside your editor? chrome --app=http://localhost:7317

Requires

Node 22.5 or newer — STICKY uses Node's built-in SQLite, so there's nothing to compile and no native modules to install.

MIT licensed. Built by Juvina.

Source: README.md at commit 2f2d73b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.