{"id":"fd93bde3-f0c7-4c7a-a001-9de76232d2e5","slug":"blitzlist","kind":"mcp","name":"Blitzlist","summary":"The universal list for hybrid human-agent teams. AI-first, MCP-native. AGPL-3.0 + commercial.","owner":"ai-fy","repoUrl":"https://github.com/ai-fy/Blitzlist","license":"AGPL-3.0","licenseTier":"strong-copyleft","trust":"community","stars":0,"match":null,"fewStars":true,"format":"mcp","createdAt":"2026-06-02T21:47:04.000Z","addedAt":"2026-10-21T06:11:59.355Z","logoUrl":"https://avatars.githubusercontent.com/u/112703532?u=32ba8f018c1701c832e481079d51d7fa8f428a34&v=4","linkOnly":false,"collection":null,"skillPath":null,"categories":["communication","cloud-infra","memory-knowledge"],"tags":["agpl","ai-agents","cloudflare-workers","d1","drizzle-orm","hono","r2","typescript"],"runtime":"binary","local":true,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":false,"reviewed":false,"syncedAt":"2026-10-24T03:55:15.231Z","sample":false,"url":"https://conduits.dev/tools/blitzlist","language":"TypeScript","transports":["stdio"],"install":{},"requirements":{"env":[],"upstreamMayCharge":false},"tools":null,"readme":"# Blitzlist\n\n> **The list for the AI era.**\n> Shared memory for hybrid human–agent teams. AI-first. MCP-native. Open-source. Self-hostable on Cloudflare in three minutes.\n\n[![License: AGPL-3.0 + commercial](https://img.shields.io/badge/license-AGPL--3.0%20%2B%20commercial-blueviolet)](./LICENSE)\n[![Status: v0.5 shipping](https://img.shields.io/badge/status-v0.5%20shipping-4cb782)](https://github.com/ai-fy/Blitzlist)\n[![MCP: 23 tools](https://img.shields.io/badge/MCP-23%20tools-a78bfa)](https://mcp.blitzlist.ai/mcp)\n[![Stack: Cloudflare Workers](https://img.shields.io/badge/stack-Cloudflare%20Workers-f48120)](https://workers.cloudflare.com/)\n\n🌐 **Try it:** [blitzlist.ai](https://blitzlist.ai) · 🔌 **MCP install:** `https://mcp.blitzlist.ai/mcp`\n\n---\n\nLists drive how we work and how we live — in boardrooms, in startups, in family kitchens, in Claude Code sessions, in sprint plans, in grocery shopping. But the AI era arrived without one.\n\nYour Claude Code todos die in 24 hours. Notion was built before AI existed. Linear retrofitted it. The list — humanity's most universal primitive of getting things done — hasn't yet entered the AI age.\n\n**Blitzlist is that list.** AI-first from the foundation. Shared between you, your team, your AI agents, and your customers through MCP. Persistent across sessions. Tracks progress automatically. Draws your attention where it's needed.\n\n---\n\n## Status\n\n**v0.5 shipping now.** The hosted MCP server is live at **`https://mcp.blitzlist.ai/mcp`** with 23 annotated tools, OAuth 2.1 + DCR, full Airtable-shaped data model (templates + lists + many-to-many memberships + flexible typed fields), per-stakeholder bearer keys, anonymous share codes with edit/comment/create permissions, and a public roadmap page at `/r/<code>` with four interactive view types (list / board / table / todo).\n\nWhat's live right now:\n\n- **MCP server**: 23 tools at `mcp.blitzlist.ai/mcp` (OAuth), `mcp.blitzlist.ai/s/mcp` (stakeholder bearer), `mcp.blitzlist.ai/c/<code>/mcp` (share-code URL)\n- **Public roadmap pages**: anyone with a share code visits `/r/<code>`, picks a view, exports to CSV / Markdown / Excel, drags cards on the kanban, ticks todos, edits state via dropdowns — all without a login when the code grants those rights\n- **Landing**: [blitzlist.ai](https://blitzlist.ai) — see the founder note + roadmap onboarding\n- **Source**: this repo. AGPL-3.0 + commercial-license tier.\n\nWhat's coming in v1.0 (the Compass + web UI for workspace owners + release-notes ergonomics + Backlog.md round-trip).\n\nWe dog-food our own product: this repo's `blitzlist/` directory IS the canonical backlog for building Blitzlist. PRs against `blitzlist/items/` propose new work; the live MCP server syncs bidirectionally.\n\n---\n\n## Why a universal list, now\n\nWork is fragmenting differently in the AI era. The same task flows between humans and agents in an hour, across multiple vendors' tools — some finishing in seconds, others running overnight. Decisions are made along the way, and the next step depends on what was decided.\n\nNo single tool captures the whole picture. **Linear sees engineering. Notion sees docs. Slack sees messages. Claude sees prompts.** Each gives you a slice. Synthesis falls on the human, who pays the cognitive tax of stitching it together — usually by hand, usually after the fact.\n\n**A universal list isn't a nice-to-have anymore. It's how you steer.**\n\n## Three frictions we erase\n\n| Friction | Today | With Blitzlist |\n|---|---|---|\n| **Context dies at session boundaries** | Your AI's todo list is gone after 24 hours; you re-explain every morning | Items, docs, files persist across sessions, weeks, releases — your AI starts every session with full memory |\n| **Artifacts don't travel** | Screenshot the deck. Copy-paste into Slack. Download the mockup. Re-upload. | Files live in R2; any MCP client reads them by reference. **The file doesn't move; references do.** |\n| **AI-to-AI handoff drops state** | Even Cowork → Code loses context. Across vendors is worse. | Every MCP-capable AI client (Claude Code, Cowork, claude.ai, others) connects to the same Blitzlist MCP server. Bridge by design. |\n\n## How it works\n\nThree audiences, each through their preferred interface, all sharing the same source of truth:\n\n```\n   Builder (Claude Code)                Stakeholder (Claude Cowork)\n         |                                       |\n         | \"Add a requirement: PR sync\"          | \"What's in v1.2?\"\n         |                                       |\n         v                                       v\n         +----------> Blitzlist MCP <-----------+\n                            |\n                            | tools return data + visual artifacts\n                            | (Mermaid diagrams, rendered summaries)\n                            v\n                     D1 + Durable Objects\n                            |\n                            | live updates\n                            v\n                  Web UI (for humans who prefer one)\n```\n\n- **Builders** use MCP from inside Claude Code, Cursor, or any MCP client\n- **Executors** (AI agents, contractors, teammates) act on items via MCP or the web app\n- **Stakeholders** (customers, OSS users, reviewers) paste a code into their own AI assistant and review the roadmap conversationally — no account, no UI to learn\n\n## What's inside\n\nTwo named products on one shared platform:\n\n### Blitzlist — the workspace\n\nThe full AI-first shared workspace. Items + sprints + documents + files + workflows + relations + roadmaps. This is what you install first.\n\n### Blitzbox — the AI-native file-sharing module\n\nInside Blitzlist (and also marketed standalone from v1.5): drop a binary, any MCP client reads it by reference. Like Dropbox, but built for the LLM workflow. Server-side text extraction for PPT, PDF, Word, Excel — your AI gets the content without you re-uploading.\n\n## Signature feature: the Compass (v1.0)\n\nA 3D animated multi-dimensional priority view that **steers both humans and AI agents** toward high-impact work. Items are spheres positioned in priority space, sized by effort, colored by risk, animated by uncertainty.\n\nThe same data drives the human visual and `get_focus()` calls from AI agents — **shared situational awareness**. A builder opens the Compass; their Claude Code session calls `get_focus()` in the background; both arrive at the same top-three items independently. No coordination needed.\n\nPer-list configurable: a backlog list shows urgency/importance/risk; a bugs list shows age/severity/customer-impact; an ideas list shows feasibility/novelty/team-excitement. Same engine, different mappings. See [ARCHITECTURE.md §3](./ARCHITECTURE.md) for the full design. **Status:** designed, scoped, scheduled for v1.0. v0.5 ships with list / board / table / todo views as the practical workspace surface.\n\n## Quick start\n\n### For end users (live now)\n\n> **Connect once per Claude surface.** MCP servers are per-client, not global. If you start a new Claude session and ask \"create a list\" but the model doesn't reach for Blitzlist tools, that session never had Blitzlist connected. Add it to every Claude surface you use.\n\n**Claude Desktop:**\n\n1. Customize → Connectors → Add Custom Connector\n2. URL: `https://mcp.blitzlist.ai/mcp`\n3. Leave auth fields empty — Claude Desktop will auto-discover OAuth, register itself, and walk you through consent in a browser tab\n\n**Claude Code (CLI):**\n\n```bash\nclaude mcp add blitzlist https://mcp.blitzlist.ai/mcp\n```\n\n**claude.ai web:**\n\nSettings → Connectors → Add custom connector → URL `https://mcp.blitzlist.ai/mcp` → authorize.\n\nThe v0.5 tool surface (23 tools, all annotated for the official MCP directory):\n\n| Category | Tools |\n|---|---|\n| **Templates** | `list_templates` |\n| **Lists** | `create_list` (with optional `items[]` to populate in one call), `close_list` (delivered/slipped/cut audit), `generate_release_notes`, `set_list_default_view` |\n| **Items — single** | `add_item`, `get_item`, `update_item`, `set_state`, `set_executor`, `comment` |\n| **Items — batch** | `add_items` (up to 200/call), `update_items`, `set_states` |\n| **Membership** | `add_item_to_list`, `remove_item_from_list`, `list_items` (with inline comments + counts) |\n| **Sharing — stakeholder keys** | `create_stakeholder_key` (returns QR + raw key, shown once), `revoke_stakeholder_key`, `list_stakeholder_keys` |\n| **Sharing — share codes** | `create_share_code` (returns QR + 4-word URL), `revoke_share_code`, `list_share_codes` |\n\nTry it:\n\n```\n> Create a shopping list with milk, bread, eggs.\n> Mark BL-001, BL-002, BL-003 as done.\n> Create a v0.5 release with these items: dashboard, migration, oauth. ship_target Sep 1.\n> Make a share code that lets reviewers comment on v0.5.\n> Generate release notes for v0.5 in customer style.\n```\n\nThe model prefers batch tools (`create_list({items:[...]})`, `add_items`, `set_states`, `update_items`) — each is a single tool call, so users see one approval prompt instead of N.\n\n### Public roadmap pages (no login required)\n\nAnyone you give a share code to opens it at **`https://mcp.blitzlist.ai/r/<code>`**. The page renders the list with full Linear-style polish — items, state pills, audit breakdown, comments, and a view switcher that lets the visitor pick:\n\n| View | What it shows |\n|---|---|\n| **List** | Items grouped by state, full cards with body + chips |\n| **Board** | Horizontal kanban columns per state; cards expand on click; drag-and-drop to change state when granted `edit` |\n| **Table** | Compact rows with state dropdown (editable) + click-to-expand description |\n| **Todo** | Checkboxes that toggle done/open in one click, no page reload |\n\nVisitors can also export the list to **CSV, Markdown, or Excel** (.xlsx) from the same page.\n\nPermissions on the share code decide what visitors can do:\n\n- `read` — view + export only (default)\n- `read + comment` — leave anonymous comments (with optional display name)\n- `read + edit` — change state via dropdown / drag / checkbox; rename and edit items\n- `read + create` — add new items to the list\n\nEither default view (`list` / `board` / `table` / `todo`) can be pinned per-list via `set_list_default_view`, or any visitor can override with `?view=board` etc.\n\n### For self-hosters\n\nManual deploy works today (one-click button lands in v1.0):\n\n```bash\n# Prereqs: Node 20+, pnpm, a Cloudflare account\ngit clone https://github.com/ai-fy/Blitzlist.git\ncd Blitzlist\npnpm install\n\n# Provision Cloudflare resources for your own account:\ncd apps/api\npnpm wrangler d1 create blitzlist-dev          # → copy database_id into wrangler.toml\npnpm wrangler kv namespace create KV\npnpm wrangler kv namespace create OAUTH_KV\npnpm wrangler r2 bucket create blitzlist-attachments\n\n# Apply schema migrations:\npnpm wrangler d1 execute blitzlist-dev --remote --file=./migrations/0000_workable_the_order.sql\n# ...repeat for each migration in apps/api/migrations/\n\n# Deploy your Worker:\npnpm wrangler deploy\n```\n\nWhat gets provisioned: a Worker (API + MCP server + roadmap renderer), D1 database, KV namespaces, R2 bucket (attachments). On the free tier the workload fits comfortably; expect ~$5/mo at light usage if you exceed it.\n\nSee [ARCHITECTURE.md §8](./ARCHITECTURE.md) for the full deployment shape and migration paths.\n\n### For contributors\n\n```bash\ngit clone https://github.com/ai-fy/Blitzlist.git\ncd blitzlist\n```\n\nRead [ARCHITECTURE.md](./ARCHITECTURE.md) for the design. Browse [blitzlist/items/](./blitzlist/items/) for the live backlog. Pick anything labeled `state: draft` or `state: proposed` and open a PR.\n\n## How it's built\n\nAll-Cloudflare for v1:\n\n- **Workers** (Hono) — API + MCP server + OAuth authorization server\n- **D1** (SQLite at the edge) — primary database; sub-millisecond queries from the Worker, no network hop\n- **Durable Objects** — one per workspace for real-time WebSocket fanout\n- **R2** — file storage with zero egress fees (the Dropbox-for-MCP economics)\n- **KV** — OAuth ephemeral state\n- **Queues** — async work (binary extraction, webhook reactions, emails)\n- **Pages** — web app\n\nOAuth 2.1 + Dynamic Client Registration via [`@cloudflare/workers-oauth-provider`](https://github.com/cloudflare/workers-oauth-provider). Drizzle ORM with SQLite dialect. TypeScript end to end. Hono is web-standards, so the API code is portable to any web-standards runtime if we ever need to leave Cloudflare.\n\nWeb app on Cloudflare Pages for v1 (Next.js via `@cloudflare/next-on-pages`). If Pages limitations bite, the web app can pull out to Vercel without affecting the Worker, D1, DOs, or R2 — see [ARCHITECTURE.md §16](./ARCHITECTURE.md) for migration paths.\n\n## Contributing\n\nTwo paths in, both first-class:\n\n### Propose a requirement (no code required)\n\nAnyone can propose a new requirement, doc, or fix without writing code:\n\n1. Fork this repo\n2. Add a file under `blitzlist/items/BL-XXX-your-slug.md` (use `XXX` as a placeholder; the sync engine assigns the real ID on merge)\n3. Open a PR\n4. Maintainers review like any code change\n\nSee [blitzlist/README.md](./blitzlist/README.md) for the file format and conventions.\n\n### Write code\n\nPick any item in `blitzlist/items/` labeled `state: draft` or `state: proposed` and open a PR implementing it. The item's acceptance criteria are the test plan.\n\nFor larger contributions or architectural questions, open a GitHub Discussion first.\n\n### Community plugins\n\nBlitzlist exposes a stable plugin API (see [ARCHITECTURE.md §17](./ARCHITECTURE.md)) for community-built integrations — Dropbox-style local-sync clients, Slack bridges, Figma extensions, IDE plugins. We define the API and conformance tests; you build the integration. n8n's community-nodes model applied to the workspace category.\n\n## Read more\n\n| Document | What's in it |\n|---|---|\n| [ARCHITECTURE.md](./ARCHITECTURE.md) | Full technical design — data model, MCP tool surface, auth, deployment, real-time, migration paths |\n| [PITCHES.md](./PITCHES.md) | Canonical positioning, three elevator pitches, taglines, hero copy — for landing pages, decks, social |\n| [blitzlist/README.md](./blitzlist/README.md) | The bootstrap convention — how the public backlog directory works |\n| [blitzlist/SYNC.md](./blitzlist/SYNC.md) | Bidirectional sync protocol between the repo and the live MCP server |\n| [blitzlist/items/](./blitzlist/items/) | The live backlog — every requirement, sprint by sprint |\n\n## Roadmap\n\n| Phase | Scope | Status |\n|---|---|---|\n| **v0.1 — Single-user spike** | Hono Worker + D1 schema + 5 core MCP tools, no auth, no web UI | ✓ shipped |\n| **v0.5 — Multi-user beta + the wedge** | Airtable-shaped data model (templates + flexible fields) · OAuth 2.1 + DCR · stakeholder access keys (per-person bearer) · share codes (anonymous diceware URLs with read/comment/edit/create perms) · public roadmap pages with list/board/table/todo views · drag-and-drop kanban · CSV/Markdown/Excel exports · release-notes generator · 23 MCP tools | ✓ shipping now |\n| **v1.0 — Production** | The Compass (3D priority visualization) · R2 attachments + Blitzbox surface · web UI for workspace owners · billing · templates ecosystem · Backlog.md round-trip interop · one-click Cloudflare deploy button | next |\n| **v1.5+** | Blitzbox as standalone landing page, Slack/SSO, local-sync community clients, public roadmap themes | |\n| **v2.0+** | Claim the shared-workspace category: rich view types, workflow automation, inline databases in docs, whiteboard, unified inbox | |\n\n## License\n\nBlitzlist is licensed under the [**GNU Affero General Public License v3.0**](./LICENSE) (AGPL-3.0).\n\nWhat this means in practice:\n\n- **Self-host freely.** Run Blitzlist for yourself, your team, or your company — no fees, no restrictions, full access to the code.\n- **Modify and contribute.** Fork it, change it, send PRs. Modifications to the codebase are welcome under AGPL-3.0.\n- **If you offer Blitzlist as a hosted service to others**, you must publish your modifications under AGPL-3.0 too. This is the network-copyleft trigger that keeps the ecosystem honest.\n\n### Commercial licensing\n\nIf your organization can't use AGPL-3.0 software (some enterprises have blanket policies), a **commercial license** is available — same code, different terms tailored to your compliance needs. Contact us via [GitHub Discussions](https://github.com/ai-fy/Blitzlist/discussions) or once we ship a contact page on blitzlist.ai.\n\n### Contributing\n\nBy contributing code, you agree to the terms in our [Contributor License Agreement](./CONTRIBUTING.md#contributor-license-agreement). The CLA is signed once per contributor via [CLA Assistant](https://cla-assistant.io/) when you open your first PR — it takes about 30 seconds. The CLA preserves the project's ability to offer commercial licensing and to evolve the license if the project's needs change in the future.\n\nThe bootstrap convention (the `blitzlist/` directory file format) is documented in [`blitzlist/README.md`](./blitzlist/README.md) and is intended as a community convention that any project can adopt freely — independent of Blitzlist's own AGPL-3.0 licensing.\n\n## Project values\n\n- **AI-first, not AI-retrofitted.** Every primitive is designed to be accessed equally by humans and agents through MCP. We don't bolt intelligence onto a UI built for browser tabs.\n- **Honest about competitors.** Linear, Notion, Backlog.md, Plane — each is excellent at part of what Blitzlist does. Our wedge is the synthesis plus the AI-first foundation, not a feature war.\n- **Open-source + self-hostable.** The community is the moat. Hosted at blitzlist.ai for those who want managed; self-hostable on Cloudflare for those who want control.\n- **Standards we build on:** Markdown (CommonMark + GFM), YAML, JSON Schema, Mermaid, MCP, OAuth 2.1 + DCR, OpenAPI, Conventional Commits, Semver, and round-trip interop with [Backlog.md](https://github.com/MrLesk/Backlog.md).\n\n---\n\nThe productivity stack was built before AI existed.\n\nLists drove every era of human work. The AI era was missing theirs.\n\n**But not anymore.**\n"}