Skip to main content
Glama
Sign In
voice-memory MCP server

voice-memory MCP server

by ryo823
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to voice-memory MCP server

No user-submitted related servers found.

    Related Servers

    • Monomem

      Monomem

      calasdan-sketch
      A
      license
      A
      quality
      B
      maintenance
      Shared memory for AI coding agents (Claude Code, Codex, Cursor and others) in one local SQLite file, over MCP or REST. Every note records which agent wrote it and keeps its history; writes that match known prompt-injection patterns are held for your review; you can roll back everything one writer did. Runs on your machine, no cloud or API keys, MIT licensed.
      9
      1,971 npm
      8
      MIT

    • kb-mcp-server

      venkateshds2u
      A
      license
      A
      quality
      B
      maintenance
      Enables users to create, retrieve, update, delete, and full-text search a local knowledge base of notes persisted in SQLite with FTS5, exposed over stdio or authenticated Streamable HTTP. It also surfaces recent/single-note resources and prompts for summarizing notes and drafting replies.
      5
      MIT

    • NoteKeeper MCP

      VRurs1606
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with tools to create, list, search, tag, and delete notes stored in a local SQLite database.
      -

    • mcp-inicio-ia

      em4nu3i69dll
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients to index and search reviewed Markdown and text documents with SQLite FTS5, read sources and prompts, manage explicit notes, and query a local Ollama assistant that uses permitted tools.
      4
      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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct access pattern: single-by-ID retrieval (get_voice_memory), keyword search (search_voice_memories), recency listing (get_recent_memories), tag enumeration (list_voice_tags), and write (save_voice_memory). An agent can easily choose between search vs. recent vs. get-by-UUID based on descriptions.

    Naming Consistency4/5

    All tools follow a verb_noun pattern (get_, search_, list_, save_), which is consistent. Minor deviation: the noun form shifts between 'voice_memory', 'voice_memories', 'recent_memories', and 'voice_tags', which is readable but not perfectly uniform.

    Tool Count5/5

    Five tools is well-scoped for a voice-memory store: one write, three read/query paths, and one tag-listing helper. Each tool earns its place without redundancy.

    Completeness3/5

    The read/create and search surface is solid, but there is no update or delete operation for memories, and no way to manage tags directly. For a memory store these are notable gaps that could cause dead ends if an agent needs to correct or remove a record.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources