Skip to main content
Glama
robertleelittleiii

warp-memory-mcp

by robertleelittleiii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to warp-memory-mcp

No user-submitted related servers found.

    Related Servers

    • artagon-vault-mcp

      artagon
      F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for querying an evidence-aware knowledge vault with temporal and provenance-aware data, supporting agent memory and semantic graph projections.
      -

    • openwhispr-mcp

      dezer32
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes OpenWhispr desktop app data—notes, folders, meeting transcripts, dictation history, and custom dictionary—to AI agents, with read and limited write operations.
      15
      12 npm
      MIT

    • voice-notes-mcp

      nikoloside
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server that exposes locally generated voice notes to any MCP client, allowing listing, searching, and reading transcripts, summaries, and knowledge graphs from voice-notes sessions.
      1
      MIT

    • AgentInspect MCP Server

      rajudandigam
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-only local MCP server for inspecting AgentInspect TypeScript AI-agent traces. Lists runs, exposes bounded causal-failure and TraceFacts evidence, evaluates TraceContract checks, compares runs, and creates share-checked evidence without mutating traces or invoking agent tools.
      14,150 npm
      638
      MIT

    • Restora

      tahabakri
      A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server that exposes your local Notion backups to AI agents — query databases, read pages, search a backed-up workspace. Offline by default: no LLM calls, no telemetry, no cloud.
      6
      1
      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

    B3.4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: status and search serve as meta/cross-cutting entry points, list_/get_ pairs cleanly separate memories, notebooks, conversations, and handoffs, and write_handoff is clearly the only write operation. Any conceptual overlap, such as search versus list_queries, is mitigated by clear descriptions.

    Naming Consistency4/5

    Most tools follow a consistent list_<plural> / get_<singular> pattern, with write_handoff fitting the verb_noun convention. The exceptions are the bare commands status and search, which would be more consistent as get_status and search_warp, but the overall pattern remains readable and predictable.

    Tool Count5/5

    Thirteen tools is well within the ideal scope and each tool has a clear role: four list/get resource pairs, a cross-resource search, a status overview, project rule listing, and a handoff write/list/get set. No tool feels redundant or superfluous.

    Completeness4/5

    The server provides strong read coverage for memories, notebooks, conversations, and recent prompts, plus a complete handoff write/list/get workflow. Minor gaps exist, such as project rules being listed only as paths without a content-read tool, but the core coordination and lookup workflows are well covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources