Yantrikdb MCP

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/yantrikos-yantrikdb-mcp

About

Use cases: agent-memory, knowledge-base

No 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, install config and code. Checked Oct 25, 2026.

Tools

5 read · 10 write · 7 delete

Secrets

None asked for

Install scripts

None found

Runs as

Python package

Tools (22)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• adminAdmin

  Cluster maintenance operations (operator-gated; master token). ACTIONS: - "maintenance_run": Run a maintenance cycle server-side. tenant=<db> for one DB, omit for all. - "maintenance_status": Worker/tenant maintenance status. Cluster (YANTRIKDB_SERVER_URL) only — in embedded mode use think(maintenance_cycle=True) instead; the engine is in-process. Args: action: "maintenance_run" or "maintenance_status". tenant: Optional single-tenant scope. split_oversized / repair_artifacts: Heavy passes (run only).

• atlasAtlasread-only

  Export this store's Memory Atlas (a static page: every memory, its entity links, claims, revision history and tasks) and serve it on 127.0.0.1. Read-only; nothing leaves the machine. ACTIONS: - "export": (default) export and serve; returns the local URL, the output directory and the exporter's report. Re-running refreshes the files under the same URL. - "status": the atlas servers this process is running. Args: out_dir: Output directory (default `<store>.atlas/` beside the store). port: Local port (0 = free one). label: Provenance label shown in the page header. open_brow…

• categoryCategorycan change or delete data

  Substitution categories for conflict detection — list, inspect, teach, or reset. ACTIONS: - "list": Show all categories with member counts. - "members": Show members of a specific category (needs category_name). - "learn": Teach new members (needs category_name + members as [[token, confidence], ...]). - "reset": Reset category to seed state (needs category_name). EXAMPLES: - category() → list all categories - category(action="members", category_name="databases") - category(action="learn", category_name="databases", members=[["tidb", 0.35]]) - category(action="reset", category_name="editors_…

• conflictConflictcan change or delete data

  Manage memory conflicts (contradictions) — list, resolve, dismiss, reclassify, or batch-burn-down the unambiguous ones (v0.8.0+). ACTIONS: - "list": List conflicts. Optional status filter. - "get": Get single conflict by conflict_id. - "resolve": Resolve with strategy: "keep_a"/"keep_b"/"keep_both"/"merge"/"dismiss". - "reclassify": Reclassify conflict type. - "auto_resolve": v0.8.0 — burn down unambiguous conflicts in one pass. Set dry_run=False to actually persist. Args: action: "list", "get", "resolve", "reclassify", "auto_resolve". conflict_id…

• conversationConversationcan change or delete data

  Bounded encrypted working-memory ring buffer for raw conversation turns (v0.9.0 engine conversation primitive). Unlike `remember` (which stores extracted semantic memories), this stores verbatim turns — useful for short-horizon working memory, e.g. "what exactly did the user say two messages ago". The ring is bounded per namespace; oldest turns evict when `max_turns` is exceeded. ACTIONS: - "record": Append a turn (needs role + content). - "recent": Retrieve last N turns, oldest-first. - "clear": Drop the buffer for a namespace. Args: action: "record" | "recent" | "clear". names…

• correctCorrectcan change or delete data

  Correct an existing memory in-place with a revision-history entry (engine v0.7.20+, Issue #47). WHEN TO USE: When the user corrects a recalled fact. - "Actually, we're using Python 3.12, not 3.11" → correct the memory. Preserves history via an append-only revision entry keyed on `reason`. Entity relationships stay attached to the same rid (in-place mutation, not a tombstone+new-rid dance). Args: rid: The memory ID to correct. reason: **Required** — why the correction was made. Non-empty. Recorded on the revision-history entry so future recall + audit can reconstruct …

• forgetForgetcan change or delete data

  Permanently forget (tombstone) one or more memories. WHEN TO USE: When the user explicitly asks to forget something, or when a memory is clearly wrong and correction isn't appropriate. Prefer `correct` over `forget` when the memory just needs updating. Args: rid: Single memory ID to forget. rids: List of memory IDs to forget (batch mode).

• gapsGapsread-only

  Surface knowledge gaps — frequently-asked, poorly-answered queries (v0.9.0 engine demand log). The substrate logs every recall and tracks how often each query is asked + what top scores it surfaces. `knowledge_gaps()` returns the queries that are asked often but answered poorly — the substrate's "known unknowns". Use this to drive proactive learning: when the agent sees a gap, it can ask the user, fetch info, or note the limitation. Args: min_count: Only surface queries asked at least this many times. max_avg_top_score: Only surface queries whose best recall score averages be…

• graphGraph

  Knowledge graph operations — entity relationships, memory↔entity links, record-to-record links, co-occurrence auto-relate, and link-expanded recall. ACTIONS: - "relate": Entity↔entity relationship (legacy). - "edges": Get all relationships for entity. - "link": Link a memory (rid) to an entity (legacy). - "search": Find entities by pattern. - "profile": Rich entity profile. - "depth": How deeply the system knows an entity. - "auto_relate": v0.8.0 — co-occurrence-driven edge backfill. Set dry_run=False to…

• memoryMemory

  Manage individual memories — get, list, search, update importance, archive, hydrate, relevance feedback, fetch a chain-shaped namespace's head, or query revision history. ACTIONS: - "get": Retrieve a single memory by rid. - "list": Browse memories with filters. - "search": Keyword substring search. - "update_importance": Change a memory's importance score. - "archive": Move to cold storage. - "hydrate": Restore archived memory. - "feedback": v0.10 — relevance feedback on a recalled memory (needs rid + fe…

• packPackcan change or delete data

  Signed, portable memory bundles — inspect, install, and trust packs. A pack is a sealed corpus another agent or vendor published. Mounted pack memories are recallable alongside your own but are DOWN-WEIGHTED (tier_multiplier < 1.0): what the user told you locally always outranks imported knowledge. READ ACTIONS (always available): - "list": Installed + mounted packs (id, name, origin, trust, rows). - "inspect": Read a pack file's manifest WITHOUT installing it. path=<file>. Shows origin, signature, embedder, rows — always inspect before you instal…

• personalityPersonality

  AI personality traits derived from memory patterns. ACTIONS: - "get": Get current personality profile. Use recompute=True to refresh. - "set": Set a trait manually (needs trait_name + score). Traits: warmth, depth, energy, attentiveness (0.0-1.0). Args: action: "get" or "set". trait_name: For set: warmth, depth, energy, attentiveness. score: For set: 0.0-1.0. recompute: For get: re-derive from memory patterns first.

• procedureProcedure

  Procedural memory — learn, surface, and reinforce strategies. ACTIONS: - "learn": Store a procedure (needs text). What worked in a specific context. - "surface": Find relevant procedures (needs query). Returns ranked by effectiveness. - "reinforce": Update effectiveness (needs rid + outcome 0.0-1.0). EXAMPLES: - procedure(action="learn", text="For this repo, always run tests before committing", domain="work") - procedure(action="surface", query="how to handle code review in this repo") - procedure(action="reinforce", rid="abc", outcome=0.9) Args: action: "learn", "surface", "reinforce".…

• recallRecallread-only

  Search memories by semantic similarity, or refine low-confidence results. MODES: - **Search** (default): recall("project architecture decisions") - **Refine**: recall("PostgreSQL vs MySQL decision", refine_from="database choice", refine_exclude=["rid1"]) ORDER: "recency" | "first_mention" (alias "chronological") | "certainty". Re-sorts the top_k already found; hints omitted. (Relevance feedback moved to memory(action="feedback") in v0.10 — recall is now purely read-only.) WHEN TO USE: conversation start (summarize the user's first message); when the user references past decisions, people, p…

• rememberRemember

  Store one or more memories in persistent cognitive memory. WHEN TO USE: Call proactively whenever the conversation reveals something worth remembering — decisions, preferences, facts about people, project context. Do NOT store ephemeral task details, code snippets, or git-derivable info. SINGLE: remember(text="User prefers dark mode", domain="preference", importance=0.7) BATCH: remember(memories=[{"text": "Alice is DevOps lead", "domain": "people"}, ...]) DRAFT: remember(summary="...long end-of-session summary...") — v0.8.0+ engine atomizes the summary into linked semantic fact…

Signals

Stars

25

Forks

9

Open issues

1

Contributors

2

Weekly downloads

139

Last commit

Oct 16, 2026 (14 days ago)

Last release

Sep 14, 2026 (1 month ago)

Last package publish

Sep 14, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.yantrikos/yantrikdb-mcp

Version

0.24.0

Auth

No auth

Packages

pypi yantrikdb-mcp

License

MIT

Repository

github.com/yantrikos/yantrikdb-mcp

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql