Skip to main content
Glama
wolfcao

muninn-local-mcp

by wolfcao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to muninn-local-mcp

No user-submitted related servers found.

    Related Servers

    • knitbrain

      PDgit12
      A
      license
      A
      quality
      C
      maintenance
      Local-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.
      37
      26 npm
      6
      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
      60 npm
      1
      Apache 2.0

    • mnemon-mcp

      nikitacometa
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server providing persistent, layered memory (episodic, semantic, procedural, resource) for AI agents, with search, versioning, and session management via a single SQLite file.
      48 npm
      3
      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 7 tools

    Disambiguation5/5

    Tools are clearly separated by scope (global vs. project-specific) using consistent prefixes, and each tool performs a distinct operation (list, search, write, delete). No ambiguity between tools.

    Naming Consistency5/5

    All tool names follow a consistent pattern: scope prefix (global_memory_ or memory_) followed by a verb (list, search, write, delete). Naming is predictable and uniform.

    Tool Count5/5

    With 7 tools covering both global and project memory operations (list, search, write, delete), the count is well-scoped and appropriate for a focused memory store server.

    Completeness4/5

    The tool surface is mostly complete for both scopes, but the global scope lacks a delete operation, which is a minor gap. CRUD operations are otherwise covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources