Cambium
Knowledge-lifecycle MCP: turn agent work into memory, recall it across projects, promote to org.
Connector by jarmstrong158 · GitHub account verified by the MCP Registry
Chalk Labs
Need help deploying Cambium?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/jarmstrong158-cambium
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.
- Tools
- 3 read · 2 write · 0 delete · 11 not yet classified
- Secrets
- None asked for
- Install scripts
- Not scanned yet
- Runs as
- Python package
Tools by what they do 16
Read from the source code; the running server may list different tools.
Read 3 · Look things up without changing anything.
recallreview_promotionsstatus
Write 2 · Create, change, send or run things.
import_memoryrecord_need
Not yet classified 11 · We could not tell from the name and description.
capturedeprecatedistillendorseexport_markdowngeneralizepromotesession_primersetupstale_reportverify_entry
Secrets and settings it asks for
Other settings (environment variables or headers).
CAMBIUM_AGENT_IDCAMBIUM_ORG_REPOCAMBIUM_REPO
Files it touches
- Any path the agent passes to its tools
Tools (16)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
captureSave a knowledge item to your LOCAL scope: a fact, design note, gotcha, or troubleshooting step worth remembering. This is the manual capture path; distill() is the automatic one. type : memory | need | skill kind : freeform subtype (note, decision, constraint, runbook, ...) why : the rationale — makes the item far more useful at recall time tags : comma/space-separated keywords (boost recall matching) valid_while : optional premise this knowledge depends on, e.g. "while we're on NetSuite" — surfaced later so a dead assumption is spottable
deprecateRetire a knowledge item so recall stops serving it — the counterpart to verify_entry (which re-affirms). This is the action stale_report points at: when an entry's premise has died ("we've left NetSuite"), deprecate it. Sets status='deprecated' wherever the item lives — local, team, or org — through the same write/CAS path promotion uses (org honours CAMBIUM_ORG_PR, landing the change as a pull request). Deprecated items drop out of recall(), KNOWLEDGE.md, and promotion, but stay in the store with a `deprecated_at` stamp and optional reason for provenance/audit; reactivating one is a manual J…
distillAutomatically turn work that already happened into knowledge. Reads two substrates natively — no export step, no copy-paste: 1. agentsync: every DONE claim on the coordination branch (task + partner note + changed files) becomes an 'outcome' memory. The note your partner left for reconciliation is exactly the knowledge worth keeping. 2. context-keeper: every active decision and constraint in .context/ becomes a memory with its rationale, preserving the dec-NNN/con-NNN provenance. Idempotent — each source record imports at most once; re-run freely (e.g. from a session-end or post-…
endorseVouch for an item — the strong trust signal, and a human judgement that nothing else in this server can substitute for. Why it matters: one endorsement fast-tracks local->team promotion, and it is REQUIRED for team->org. Recall counts alone never reach org scope, by design — popularity is not correctness, so somebody has to deliberately say "this is right" before knowledge becomes org-wide. When to use this instead of the alternatives: endorse : you have CONFIRMED the item is correct and want it to carry more weight and become promotable. verify_entry : you re-ch…
export_markdownRender knowledge to a human-readable KNOWLEDGE.md — grouped by scope then project, each item showing summary, kind, provenance (dec-NNN / claim origin), recall count and promoted date. cp1252 mojibake (em dashes, curly quotes) is normalized so the text is clean. scope='org' (default): re-render the org knowledge repo's KNOWLEDGE.md from its knowledge.json and commit + push it beside the JSON, so the org repo's docs are always current. (This also runs automatically after any org promotion — direct-push commits both files together; PR mode puts both on the same PR branch.) scope='local'|'team'…
generalizeRestate an ALREADY-PROMOTED item's body as the cross-project rule, in place, keeping the concrete version as `example`. The remediation counterpart of the org generalization gate: items that reached org (or team) before the gate — or were forced past it — are listed by review_promotions() under `org_needs_generalization`; this rewrites one to its general form. org_content : the cross-project rule to become the body. If omitted, the item's latest endorsement note is used (that is where the generalization was usually already written). note : optional note reco…
import_memoryIngest an external memory export into cambium as LOCAL-scope, provenance- tagged knowledge items — a source adapter alongside distill's substrate readers. Import/ingest only: it reads the source READ-ONLY and never writes back to it. source : adapter name. 'json' = a generic JSON/JSONL export — a list of records (or an object wrapping one under memories/items/records), each with a text body (content/text/body/memory/note) plus optional title, why, kind, tags, id, timestamp. It's the extension point: new formats are new adapters, no core changes. path : lo…
promoteGraduate knowledge up a scope as it earns trust — the compound-growth step. With no arguments, scans your local items and promotes every one that qualifies to team. With an item_id, promotes that item one level (local->team, or team->org with to_scope="org"). Thresholds: local->team needs recalls >= CAMBIUM_PROMOTE_RECALLS or one endorsement; team->org always needs an endorsement (force=True overrides, use deliberately). Org promotion lands as a direct push, or as a pull request when CAMBIUM_ORG_PR=1 — the PR review is the org trust gate. org_content : the cross-project restatement of a body…
recallSearch knowledge across scopes and return the best matches. THE read endpoint for every agent type — a coding agent, a Slack KB bot, an SRE bot — they all ask here, so knowledge captured once serves them all. scope : auto (local+team+org, the default) | local | team | org limit : max results Every returned item's recall counter is incremented (local directly, team best-effort via the shared branch) — usage is the trust signal promotion feeds on. If nothing clears the relevance floor the response says no_confident_match: true — don't present weak matches as established fact.
record_needRecord a NEED — something missing, wanted, or blocking. Needs are first-class alongside memories: "we need staging seeds", "docs for X are missing", "no way to replay a failed job". When to use this instead of the alternatives: record_need : a GAP. Something that does not exist yet and should. capture : a FACT you learned. Use it when the thing is already true. distill : never called by hand for this — it imports work that already happened, and cannot invent a need. Side effects: appends one item to the LOCAL knowledge store on this machine (personal scope) and …
review_promotionsWhat's ready to move up? Lists local items eligible for team, team items eligible for org (endorsed), and org PRs already opened. The human-readable checkpoint before running promote().
session_primerA compact digest of what's ALREADY known for this project — built to be injected automatically at session start so recall is passive, not a step an agent has to remember. Returns the highest-value active knowledge (most- recalled, then most-recently-updated) across local+team+org, plus any promoted assumptions (valid_while premises) that look stale and worth re-checking. READ-ONLY: unlike recall(), it does NOT increment recall counters — a passive session-start surfacing must never inflate trust or nudge promotion. It is the session-start counterpart to distill() at session end: together they…
setupFinish cambium's setup in one call — the tool status() and every unconfigured error point you to. Validates paths, scaffolds .cambium/ (and gitignores it), and writes a local fallback config the server reads when env vars are absent (env still wins when set, and it takes effect immediately — no restart). project_repo : absolute path to your project's git clone (required) agent_id : your unique agent id (required) org_repo : optional — a local clone path, OR a GitHub 'owner/name'. If a name isn't cloned locally, setup OFFERS the exact gh/git commands to st…
stale_reportWhich promoted knowledge might be going stale? Lists team + org entries (the ones that cleared the trust gate) sorted OLDEST-VERIFIED-FIRST, with never-reverified entries flagged at the top and each entry's valid_while premise surfaced so a reader can spot dead assumptions ("while we're on NetSuite" long after the NetSuite migration). project : limit to one project's entries (default: all) older_than_days : only entries last verified more than N days ago (plus every never-verified one); 0 = no age filter. Event-driven, not clock-driven: this reports absent/old verif…
statusFirst thing to call — especially when cambium looks broken. Returns structured config state: what's set, what's missing, what each gap costs in plain terms, and the exact setup() call that fixes it. NEVER raises on missing config. When fully configured it also reports item counts per scope/type, distill watermarks, and which substrates are actually wired.
Show 1 more tools
verify_entryConfirm a knowledge entry still holds — stamp its last_verified to now. This is the event that keeps promoted knowledge honest: promotion's trust gate defends what comes IN, verification keeps an entry from silently going stale after. An optional note records what was confirmed. Absent/old last_verified is a signal (see stale_report), never an automatic downgrade. Works on local and team entries; find stale ones with stale_report().
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Weekly downloads
- 35
- Last commit
- Aug 6, 2026 (2 months ago)
- Last release
- Aug 2, 2026 (2 months ago)
- Last package publish
- Aug 2, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.jarmstrong158/cambium- Version
- 0.2.0
- Auth
- No auth
- Packages
- pypi cambium-mcp
- License
- PolyForm-Noncommercial-1.0.0
- Repository
- github.com/jarmstrong158/cambium
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
More from jarmstrong158
- 0.576score
Context Keeper
jarmstrong158
Durable project-memory MCP: decisions, constraints, and pipelines across Claude sessions.
ConnectorBFreshness: BLocal★ 1↓ 114/wkClaude Code +5 - 0.565score
Skillmatch MCP
jarmstrong158
Job search and ranking pipeline via MCP for Claude Desktop.
ConnectorBFreshness: BLocal★ 2↓ 48/wkClaude Code +5 - 0.565score
agentsync (remote)
jarmstrong158
Cloudflare Worker remote transport for agentsync.
ConnectorBFreshness: BRemote★ 1Claude Code +3 - 0.554score
agentsync
jarmstrong158
Multi-agent coordination MCP: claim work, survey peers, resolve conflicts via a git branch as CAS.
ConnectorBFreshness: BLocal↓ 53/wkClaude Code +5 - 0.541score
cambium (remote)
jarmstrong158
Cloudflare Worker for read-only recall of cambium knowledge.
ConnectorBFreshness: BRemoteRead-onlyClaude Code +3 - 0.541score
Context Keeper (remote)
jarmstrong158
Cloudflare Worker remote backend for context-keeper (D1).
ConnectorBFreshness: BRemoteClaude Code +3
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get Cambium running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
Cambium MCP server. Agent Mart. https://agentmart.dev/connectors/jarmstrong158-cambium (last updated 2026-10-24)