An MCP server, 48 tools
A Model Context Protocol server that lets an AI agent operate the archive — 48 documented tools.
{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }{ "jsonrpc": "2.0", "id": 1, "result": { "tools": [ "create_item", "bulk_create_items", "search_items", "archive_item", "restore_item", … 43 more ] } }Real names — this repository is public.Context & problem
Once the archive existed, the thing that most wanted to write to it was not a person at a keyboard. A Model Context Protocol server exposes it as tools an agent can call: boards, items, notes, bookmarks, goals, folders, templates, automations and workspaces, grouped into 48 of them. Installed by pointing a client at the repository with a single required environment variable, and running against his own VPS behind a secure tunnel.
Role
Sole developer.
Constraints
- Installed by people on four different operating systems and two different clients.
- One required environment variable. Anything more is a setup someone abandons.
- The tool surface is the documentation — an agent reads the catalogue, not a manual.
Decisions & why
- Bulk operations are their own tools, not loops over single ones.
- An agent asked to create twelve items should make one call. Twelve round trips is twelve chances to half-finish.
- Deleting an item archives it, and restoring it is a separate tool.
- The caller is a language model. Destructive by default is the wrong default when the caller can be confidently wrong.
What it does now
Public, and the only one of the nine whose code can be read. It installs straight from the repository with npx.
Stack
- TypeScript
- Node.js
- Model Context Protocol