LLMemory MCP Server
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):
Log in to the Cline Dashboard → Organization → MCP Servers
Add a new Remote MCP server
Name:
LLMemory· URL:https://mcp.llmemory.xyz/mcpSave. In VS Code/JetBrains, open the Cline panel → MCP Servers → connect
llmemory.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):
{
"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/mcpOpen WebUI — Admin Settings → External Tools → add Streamable HTTP MCP server with URL
https://mcp.llmemory.xyz/mcp
Tools
Tool | Purpose |
| Show which AI providers have data in your vault and counts |
| Recently updated conversations (id, title, source, message count). Filter by |
| Full-text search across all imported conversations. Returns snippets + conversation IDs |
| Fetch one full transcript by ID (Markdown or JSON) |
| Agent-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.filescope).
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_recentfiltered tocodex, thenget_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
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/meir-may/llmemory-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server