
Agendum
io.github.sralliPublished by GitHub account sralliv0.3.4Updated Oct 24, 2026
AI agent memory: task tracking, scoped work packages, decisions, and cross-session continuity
Overview
Gives AI coding agents persistent project memory: task boards, scoped work packages, decisions, and cross-session continuity.
- What you can do
- Agendum is a local MCP server that stores project state for coding agents. It exposes 14 pm_* tools: pm_ingest imports a Markdown plan into board items with dependencies, pm_next returns the next scoped work package with enriched context, and pm_done records decisions, patterns, and learnings while unblocking dependents. pm_memory, pm_learn, pm_search, pm_consolidate, and pm_supersede manage searchable knowledge, and pm_status shows a dashboard. State is kept as human-readable Markdown and YAML under ~/.agendum/ or a project-local .agendum/ directory.
- When to use it
- Use it when an agent works on multi-step coding projects across several sessions and needs to remember decisions, respect task scope, and follow a dependency order. It fits plan-driven workflows where a Markdown plan is turned into bounded tasks. It is less useful for one-off, single-session requests.
- Requirements
- A local Python runtime; install via pip or run with uvx. No accounts, API keys, or environment variables are declared. Optional vector search requires the agendum[vectors] extra. It runs as a stdio process on the user's machine and is desktop-only.
Installation
In SourceWeft
- Open Agendum in the dashboard and add it to a workspace.
- 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
agendum
[PyPI version] [Downloads] [Python 3.13+] [Tests] [License: MIT]
Project memory and scoping engine for AI coding agents.
AI coding agents are stateless — they forget between sessions, lose decisions, and have no way to scope complex work. agendum is an MCP server that gives any agent (Claude Code, Cursor, Windsurf, Cline, and others) persistent project state, bounded work packages, and cross-session continuity.
Quick Start
Works with any MCP client — see setup for Cursor, Windsurf, VS Code, and others.
How It Works
Each pm_done records decisions and patterns that enrich future pm_next calls — context compounds across sessions.
Example session:
14 MCP Tools
Setup & Orientation
Planning & Backlog
Execution Loop
Knowledge & Search
Hybrid Search
pm_search combines three signals to find relevant knowledge across memory, learnings, and completed board items:
- FTS5 with Porter stemming —
authmatchesauthentication,configmatchesconfiguration. Always on, zero config. - Vector search (optional) — Install
agendum[vectors]to add semantic similarity viafastembed+sqlite-vec. Activates automatically alongside FTS5. - Entity graph — Topics and tags form a knowledge graph. Entries sharing 2+ entities are linked automatically. Graph expansion surfaces related knowledge that keyword search misses.
All three signals are fused via Reciprocal Rank Fusion (RRF), then reranked by recency and access frequency. The index rebuilds from Markdown files — no data loss if it gets corrupted.
Key Capabilities
- Adaptive context budget — enrichment scales with task complexity: 4K chars for trivial tasks, up to 10K for large ones
- Verification gate —
pm_done(verified=True)distinguishes tested from untested completions - Git auto-extract —
pm_donereadsgit diffandgit logautomatically when no files are specified - Pluggable enrichment pipeline — four context sources injected into every work package: project rules (CLAUDE.md/AGENTS.md), memory, dependency context, learnings
- Dependency resolution — topological ordering with cycle detection; dependents unblock automatically when upstream tasks complete
- Memory health —
pm_statuswarns about corrupted entries;pm_consolidatestrips XML fragments, deduplicates, and flags contradictions - Zero config — auto-initializes on first tool call, derives board name from git remote
- Git-native storage — all state is human-readable Markdown + YAML in
.agendum/, diffable and committable
Installation
All MCP clients except VS Code use the same config. Add to the appropriate file:
VS Code (GitHub Copilot): Uses
"servers"instead of"mcpServers". Add to.vscode/mcp.json:
CLI (standalone)
Storage Layout
All state lives in ~/.agendum/ (or .agendum/ in your project if you prefer local storage):
Architecture
Development
License
MIT
Source: README.md at commit 369519a
Tools
0Version history
1- v0.3.4LatestSep 16, 2026
Score
50% 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