Skip to main content
Glama
Sign In
warp-memory-mcp

warp-memory-mcp

by robertleelittleiii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Warp Memory MCP Server

Read-only access to local Warp / Oz data so other agents (Grok, Claude, etc.) can coordinate with Warp’s AI.

Warp’s official Agent Memory lives on Oz (cloud, research preview, no public API yet). This server does not talk to that API. It reads what Warp stores on this Mac and a small sidecar used for Grok ↔ Oz handoffs.

What is available locally

Source

In warp.sqlite

Notes

Saved memories (AIFACT)

generic_string_objects

“Remember this” items Oz wrote locally

Notebooks / plans

notebooks

Full Warp Drive plan text

Conversations

agent_conversations

Title, first prompt, artifacts — not the transcript

User prompts

ai_queries

The text you typed to Oz

Project rules

project_rules

Paths to AGENTS.md / WARP.md

Oz cloud Agent Memory

—

Not accessible

Full chat transcripts

—

Cloud-only when Cloud Conversation Storage is on

Related MCP server: artagon-vault-mcp

Prerequisites

uv is enough. No Full Disk Access is required — the Warp DB lives in a Group Container, not ~/Library/Messages.

If Warp is running, the DB is opened read-only with a busy timeout.

Running

uv run --project /Users/rlittle/Development/warp-memory-mcp \
  /Users/rlittle/Development/warp-memory-mcp/server.py

Override the database path with WARP_SQLITE if needed.

Client config

Registered in:

  • ~/.grok/config.toml as warp-memory (Grok)

  • ~/.warp/.mcp.json as warp-memory (Oz can read Grok handoffs)

Restart Grok after adding the server so the tools appear.

Tools

Tool

Description

status

What is readable vs cloud-only, plus counts

list_memories / get_memory

Saved Warp AIFACT memories

list_notebooks / get_notebook

Warp Drive notebooks / plans

list_conversations / get_conversation

Session summaries + linked plans + prompts

list_queries

Recent user prompts to Oz

search

One search across memories, notebooks, conversations, prompts

list_project_rules

Warp project rule files

write_handoff / list_handoffs / get_handoff

Sidecar notes between Grok and Oz

Handoffs are JSON files under ~/.warp/agent-coordination/handoffs/. They are not written into warp.sqlite, so they will not fight Warp Drive sync.

Typical questions this answers

What did Oz prepare to work on tonight?
Search Warp notebooks for scan_processing.
Show the latest Oz conversation and its user prompts.
Write a handoff to Oz that Grok will do ScanImporter locking on 3.4beta.

Safety

  • Warp’s database is read-only.

  • Command history (commands table) is not exposed.

  • agent_tasks protobuf blobs are not exposed.

Available Tools

13 tools
get_conversationB

Get one Warp conversation: summary, linked plan notebooks, and the user prompts from that session.

Inputs: id_or_conversation_id (required), query_limit.

get_handoffA

Read one handoff note by id.

Inputs: id (required).

get_memoryA

Get one Warp saved memory by numeric id or name.

Inputs: id_or_name (required).

get_notebookB

Get a Warp notebook / plan by id, title, or document uid.

Inputs: id_or_title (required).

list_conversationsB

List recent Warp agent conversations (title, first prompt, linked plans). Transcripts are not stored locally.

Inputs: limit, query, working_directory.

list_handoffsC

List Grok ↔ Oz coordination handoffs.

Inputs: limit, to_agent.

list_memoriesA

List Warp saved memories (local AIFACT 'remember this' items).

Inputs: query.

list_notebooksC

List Warp Drive notebooks / agent plans (full plans live here).

Inputs: query, include_body.

list_project_rulesA

List Warp project rule files (AGENTS.md / WARP.md paths).

Inputs: no named parameters.

list_queriesC

List recent user prompts sent to Warp / Oz.

Inputs: limit, query, conversation_id, working_directory.

searchA

Search Warp memories, notebooks/plans, conversation summaries, and recent user prompts to Oz. Best first tool for 'what did Oz work on' / 'find the Warp plan'.

Inputs: query (required), limit, sources.

statusA

Describe what Warp / Oz data is readable locally versus cloud-only. Use this first when coordinating with Warp's AI.

Inputs: no named parameters.

write_handoffC

Write a coordination note between Grok and Oz. Stored under ~/.warp/agent-coordination/handoffs (not in warp.sqlite).

Inputs: body (required), title (required), tags, to_agent, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    ActivityInactive
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    • voice-notes-mcp

      nikoloside
      A
      license
      Not graded
      quality
      D
      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

    • 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.
      -

    • 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,507 npm
      212
      MIT