Skip to main content
Glama
yantrikos

YantrikDB MCP

by yantrikos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to YantrikDB MCP

No user-submitted related servers found.

    Related Servers

    • dakera-mcp by Dakera-AI

      dakera-mcpofficial

      Dakera-AI
      F
      license
      A
      quality
      B
      maintenance
      Self-hosted MCP-native agent memory server. Gives AI agents persistent, decay-weighted memory via 83 MCP tools — no cloud, full control. RocksDB+HNSW backend. Works with Claude Code, Cursor, and any MCP-compatible agent.
      14
      8
      -

    • agentmemo-mcp

      andrewpetecoleman-cloud
      A
      license
      A
      quality
      D
      maintenance
      Persistent memory and human approval for any AI agent. Give your AI agents the ability to remember across sessions and ask humans for approval before sensitive actions. Works with Claude, Cursor, OpenClaw, and any MCP-compatible client.
      6
      2 npm
      MIT

    • kontexta

      safiyu
      A
      license
      A
      quality
      A
      maintenance
      A local-first MCP server that gives AI coding agents persistent memory and controlled commands. Features a git-backed markdown knowledge vault with FTS5 search, surgical section edits, token-aware context budgeting, and a sandboxed command engine with human approval gates. Works with Claude Code, Cursor, Copilot, Gemini, and more.
      4
      58
      249 npm
      1
      Apache 2.0

    • memex

      iamtouchskyer
      A
      license
      Not graded
      quality
      A
      maintenance
      Zettelkasten-based persistent memory for AI coding agents. Auto-saves atomic knowledge cards with \[\[bidirectional links]] after tasks and auto-recalls before new ones. No vector DB — plain markdown files with git sync. Works as Claude Code plugin or MCP server for Cursor, VS Code Copilot, Codex, and Windsurf.
      110 npm
      142
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target a distinct subsystem—write/retrieve/correct/forget memories, graph, temporal, conflicts, triggers, sessions, tasks—and action enums keep sub-operations separate. The main ambiguity is procedure vs skill, which both store and surface reusable knowledge, and memory/recall/temporal overlap in retrieval but with clear usage notes.

    Naming Consistency4/5

    All tools are single lowercase tokens, which is a consistent style, but there's no verb_noun convention and names mix nouns (memory, graph) with verbs (remember, forget, recall, think). The action-based subcommands add internal consistency, so the overall pattern is predictable.

    Tool Count3/5

    21 tools is on the heavy side for one server, and several tools (category, personality, pack) serve niche features. Still, the server's scope is broad—memory, graph, temporal, conflict, session, task, skill—so the count is defensible but borderline.

    Completeness5/5

    The surface covers the full memory lifecycle (create/read/update/delete/correct), multiple retrieval modes, graph relationships, conflict resolution, maintenance, sessions, tasks, and even pack import/export. There are no obvious dead ends for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources