Midas
Local-first, source-traceable agent memory — no LLM at ingest, fully offline
Connector by vornicx · GitHub account verified by the MCP Registry
Chalk Labs
Need help deploying Midas?
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/vornicx-midas
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
- 14 read · 5 write · 4 delete
- Secrets
- None asked for
- Install scripts
- Not scanned yet
- Runs as
- Python package
Tools by what they do 23
Read from the source code; the running server may list different tools.
Read 14 · Look things up without changing anything.
audit_usebuild_contextcheck_forbidden_actioncheck_memory_useinspect_memorymemory_conflictsmemory_diffmemory_policymemory_stateopen_loopsproject_staterecall
Show 2 more tools
resumestats
Write 5 · Create, change, send or run things.
captureclose_looprememberremember_coderemember_commitment
Delete 4 · Delete, drop, revoke or wipe things.
forgetforget_allforget_matchingmaintain
Secrets and settings it asks for
Other settings (environment variables or headers).
MIDAS_MCP_DBMIDAS_MCP_EMBEDDERMIDAS_MCP_MAX_RECORDSMIDAS_MCP_MIN_IMPORTANCE
Tools (23)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
audit_useAudit memory useread-onlyThe compliance audit artifact for a memory-justified use: the guard decision + the full provenance and belief-revision history of every supporting memory + an attributability score (fraction of evidence with both a source and an actor). Hand this to an auditor to prove WHY an action is or isn't justified. Source-traceable, deterministic, no LLM.
build_contextBuild contextread-onlyAssemble a budgeted, prompt-ready context block (lean dated lines + a 'Today is' anchor). Use recall/inspect_memory for full provenance.
captureCapture turnOffer a turn to memory; Midas decides whether to keep it (no LLM): scores importance, enforces the relevance floor, skips duplicates, and says why. kind: note | chat | fact | preference | constraint | mission. provenance: planning | action | observation | user_confirmation.
check_forbidden_actionCheck forbidden actionread-onlyBefore a code action, check it against the project's live `forbidden_action` rules. Two tiers, by confidence (deterministic, no LLM; superseded/retired rules ignored): - `forbidden` (HIGH confidence, lexical match) → do NOT do it; refuse and cite `rules`. - `possibly_forbidden` (ADVISORY, semantic/paraphrase match) → ASK the user before proceeding; the semantic signal is noisy (~31% false positives, `eval.forbidden_eval`), so it warns, not blocks. Separate from the provenance/currency gate (`check_memory_use`).
check_memory_useCheck memory useread-onlyDecide whether recalled memory may justify the intended use. intended_use: planning | answer | external_action | destructive_action (the last two require user_confirmation provenance).
close_loopClose loopClose an open commitment: records the resolution and supersedes the open loop, keeping the promise -> resolution history auditable. Get loop_id from open_loops.
forgetForget memorycan change or delete dataDelete a single memory by id (supersession chains are relinked, not orphaned).
forget_allForget allcan change or delete dataClear all stored memories (fresh start).
forget_matchingForget matchingcan change or delete dataTopic-level erasure with a reviewable audit. DRY RUN by default: returns what WOULD be deleted; repeat with dry_run=false to erase. Bypasses durability protections on purpose.
inspect_memoryInspect memoryread-onlyInspect one stored memory by id without search, mutation, or embedding exposure.
maintainMaintain memorycan change or delete dataRun a no-LLM memory-maintenance pass (bound to max_records and/or drop below min_value) and return the deletion audit. Durable kinds and supersession chains are protected.
memory_conflictsMemory conflictsread-onlyLive beliefs that CONTRADICT each other with neither superseding the other — the multi-agent failure mode. Ranked candidate pairs (same-slot heuristic: value swap / numbers disagree / one side negates). Verify with the user, then forget the wrong one or capture the corrected value.
memory_diffMemory diffread-onlyWhat CHANGED in memory in the last `hours`: beliefs newly added, and beliefs revised (old -> new). The 'what's new since our last session' view for resuming long-horizon work without re-reading everything. Deterministic, no LLM.
memory_policyMemory policyread-onlyReturn the exact MCP-injected memory policy text and guard parameters.
memory_stateMemory stateread-onlyThe CURRENT durable state of a project/scope: the live (non-superseded) decisions, constraints, facts, and preferences, newest first. Use this to ONBOARD into a project or before planning — when a broad 'what's the current state?' has no single matching turn, so `recall` under-retrieves. Not a similarity search and no LLM. kinds: optional comma list (constraint,fact,preference,mission) to narrow; empty = all durable kinds.
Show 8 more tools
open_loopsOpen loopsread-onlyUnresolved commitments — work someone said WOULD be done and never closed — oldest (most overdue) first. Record one with remember_commitment; close it with close_loop.
project_stateProject stateread-onlyThe current code-state of a project for a coding agent, grouped by code_kind (architecture_decision, bug_fixed, convention, forbidden_action, dependency_choice, ...). Live (non-superseded) memories only — call this to ONBOARD into a project, or to see what is decided and what is forbidden before acting. Deterministic, no LLM. Capture code memories with the SDK's `midas.coding.remember_*` helpers (they tag `code_kind` + `project`).
recallRecallread-onlyRetrieve relevant memories with deterministic, source-traceable evidence (exact stored text + provenance/source/timestamps + score components). Set hybrid=true for exact-identifier queries.
rememberRememberStore a memory for later recall. kind: note | chat | fact | preference | constraint | mission. importance 1-5 (0 = auto-derive from content, no LLM). provenance: planning | action | observation | user_confirmation (external actions may rely only on user_confirmation).
remember_codeRemember code memoryCapture a CODE memory tagged by category + project, for the coding-agent views. code_kind: one of architecture_decision | dependency_choice | convention | bug_fixed | recurring_failure | forbidden_action | command_worked | command_failed. Use forbidden_action for rules the agent must not violate (they gate `check_forbidden_action`); afterwards `project_state` shows the live state by category. No LLM. Set provenance="user_confirmation" only when the user explicitly confirmed it.
remember_commitmentRemember commitmentRecord a commitment (an OPEN LOOP): promised work that stays visible in open_loops/resume until closed with close_loop, so promises survive across sessions.
resumeResume sessionread-onlySTART OF SESSION: everything needed to pick up where the last session left off, in ONE call — pinned directives, forbidden rules, what changed in the last `hours` (default: a week), current state, open commitments, and unresolved conflicts. `context` is prompt-ready and token-budgeted.
statsMemory statsread-onlyMemory stats: total, by kind/provenance/namespace, and short/medium/long temporal tiers.
Signals
- Stars
- 15
- Forks
- 3
- Open issues
- 1
- Weekly downloads
- 37
- Last commit
- Jul 28, 2026 (3 months ago)
- Last release
- Jul 8, 2026 (3 months ago)
- Last package publish
- Jun 7, 2026 (4 months ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.vornicx/midas- Version
- 0.0.1
- Auth
- No auth
- Packages
- pypi midas-memory-mcp
- License
- MIT
- Repository
- github.com/vornicx/Midas
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
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 Midas 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
Midas MCP server. Agent Mart. https://agentmart.dev/connectors/vornicx-midas (last updated 2026-10-24)