LLMemory

io.github.meir-mayPublished by GitHub account meir-mayv0.1.0Updated Oct 27, 2026

Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only

The publisher's own server: Memory.fit

VerifiedStreamable HTTPWeb executableFiles & StorageKnowledge & Memory

Overview

AI-generated overview

Remote MCP server that lets an assistant search and pull context from your imported ChatGPT, Claude and Codex chat history stored in your own Google Drive.

What you can do
  • List which AI providers have imported data in your vault, with counts
  • List recent conversations, optionally filtered by source
  • Full-text search across all imported conversations, returning snippets and conversation IDs
  • Fetch a full transcript by ID as Markdown or JSON
  • Build an agent-ready context pack (goal, recent state, files, open tasks) for a conversation or folder
When to use it
Useful when you want a coding agent or chat client to recall earlier work discussed in ChatGPT, Claude or Codex sessions without copy-pasting transcripts, for example asking what you decided about a project last week or pulling a recent session's context.
Requirements
A remote Streamable HTTP endpoint; no local install or package. OAuth 2.1 with dynamic client registration and a browser flow on first tool call, authorizing a Google account and granting Drive access. Your chat history must already be exported into an LLMemory folder in that Google Drive by the LLMemory browser extension or CLI. The client must support Streamable HTTP and OAuth.
Before you install
Grants the server access to your Google Drive LLMemory folder via the drive.file scope, so you are trusting a third-party service with OAuth brokering to your Drive. It is described as read-only and zero-storage, but chat content is streamed through the provider's Cloudflare Workers infrastructure. Review the stated privacy posture before connecting a work or personal Google account.

Installation

In SourceWeft

  1. Open LLMemory in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.meir-may%2Fllmemory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "llmemory": {
      "type": "http",
      "url": "https://mcp.llmemory.xyz/mcp"
    }
  }
}

README

LLMemory MCP Server

A remote MCP server that lets AI coding agents search and pull context from your imported AI chat history (ChatGPT, Claude, Codex, Claude Code) without copy-pasting. Reads your vault live from your own Google Drive. Zero server-side storage, fully private.

Server URL: https://mcp.llmemory.xyz/mcp Transport: Streamable HTTP Auth: OAuth 2.1 with Dynamic Client Registration (no API keys — browser flow on first use)

Install in Cline

This is a remote MCP server — no cloning, no npm install, no local process. Cline just needs the URL.

Option A — Cline Dashboard (recommended):

  1. Log in to the Cline Dashboard → Organization → MCP Servers
  2. Add a new Remote MCP server
  3. Name: LLMemory · URL: https://mcp.llmemory.xyz/mcp
  4. Save. In VS Code/JetBrains, open the Cline panel → MCP Servers → connect llmemory.
  5. On first tool call, a browser window opens — authorize with Google and grant Drive access.

Option B — Cline MCP config JSON: Add this to your Cline MCP settings (cline_mcp_settings.json):

json
{  "mcpServers": {    "llmemory": {      "type": "remote",      "url": "https://mcp.llmemory.xyz/mcp"    }  }}

Restart the Cline extension. On first tool call, the OAuth browser flow opens automatically.

Install in other MCP clients

Same URL works in any MCP client that supports Streamable HTTP + OAuth 2.1:

  • Cursor — LLMemory Cursor plugin
  • VS Code / GitHub Copilot — add to .vscode/mcp.json: { "servers": { "llmemory": { "type": "http", "url": "https://mcp.llmemory.xyz/mcp" } } }
  • Claude Desktop / Claude Code — claude mcp add --transport http llmemory https://mcp.llmemory.xyz/mcp
  • Open WebUI — Admin Settings → External Tools → add Streamable HTTP MCP server with URL https://mcp.llmemory.xyz/mcp

Tools

ToolPurpose
list_sourcesShow which AI providers have data in your vault and counts
list_recentRecently updated conversations (id, title, source, message count). Filter by source
search_chatsFull-text search across all imported conversations. Returns snippets + conversation IDs
get_conversationFetch one full transcript by ID (Markdown or JSON)
get_context_packAgent-ready briefing (goal, recent state, files, open tasks) for one conversation or a whole folder

What it reads

LLMemory reads the LLMemory/ folder in your Google Drive — a manifest.json plus one JSON file per conversation, written by the LLMemory browser extension or CLI. The server is read-only and zero-storage: it brokers Google OAuth, streams the result, then forgets everything. Your chats never leave your Drive on a server.

Privacy

  • Zero server-side storage. No chat content, no per-user database. Cloudflare Workers free tier.
  • Your Drive is the storage. Chats live in your own Google Drive LLMemory/ folder.
  • Read-only. The connector never writes to your vault.
  • OAuth-scoped. The server only ever sees your LLMemory/ Drive folder (drive.file scope).

Full privacy posture: STORE_PRIVACY.md

Examples

  • "What did I figure out about the OAuth worker last week?" → searches your vault
  • "Pull my most recent Codex session" → list_recent filtered to codex, then get_conversation
  • "Give me a context pack for the session where we built the Claude connector" → get_context_pack
  • "Show me which chats have data imported" → list_sources

Links

License

MIT

Source: README.md at commit e43cc59

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Memory integrations