HyperFrames by HeyGen
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
MCP server for browsing, searching, exporting, and backing up your Cursor AI chat history
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
One time only; it works for every server that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"cursor-history": {
"command": "npx",
"args": [
"-y",
"cursor-history-mcp"
]
}
}
}Use Cursor History and tell me what you can do for me, then show me one thing✓ If Claude says it is using Cursor History or shows a Cursor History tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Cursor History yet
Cursor History runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Cursor History
B · Others in Chat & email that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user cursor-history -- npx -y cursor-history-mcpYou should see Cursor History listed as connected
Use Cursor History and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Cursor History or shows a Cursor History tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Cursor History and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Cursor History or shows a Cursor History tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Cursor History and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Cursor History or shows a Cursor History tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user cursor-history -- npx -y cursor-history-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"cursor-history": {
"command": "npx",
"args": [
"-y",
"cursor-history-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"cursor-history": {
"command": "npx",
"args": [
"-y",
"cursor-history-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"cursor-history": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cursor-history-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 14, 2026
The registry name was verified with the GitHub account S2thend, which owns the repo
Code last changed 2 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 months ago, and the latest version (0.3.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: HyperFrames by HeyGen, Inbox Zero, draw.io
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
Search Gmail and Outlook, save drafts, manage email rules, and view email stats.
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
English | 中文 | Français | Español
Let your AI search your Cursor history.
Your existing Cursor conversations may already contain months of decisions, bugs, fixes, and architectural context. Give an MCP-capable assistant a way to find that context—without having recorded it with this tool beforehand.
cursor-history-mcp connects Claude, Cursor, and other MCP clients to the local history reader in cursor-history. Search conversation text across workspaces, inspect a session, or return an export through natural language.
No embeddings, indexing service, or API key is required by this server. Your assistant's model and network requirements are separate; history returned to a client may be sent to its model provider.
MCP-exclusive: [Year in Review](#year-in-review). Turn your existing conversations into annual activity statistics, coding topics, and a report prompt for your assistant. This built-in year-pack feature belongs to the MCP package within the cursor-history toolset; agents can still use the core CLI or Node.js API directly for history access.
“Have we solved this authentication bug before? Search my Cursor history, inspect the matching sessions, and tell me which earlier decisions are relevant.”
Quick start · Year in Review · Storage support · Tools · Safety · CLI / Node.js companion
Requires Node.js 20.x or 22.x–26.x, readable local Cursor history, and a client that supports local stdio MCP servers. The client must run the server on the machine where that history is available.
Version scope: these docs describe cursor-history-mcp@0.3.1, powered by cursor-history@0.18.0. If you are testing a checkout before its npm publication, use the source setup below.
Client compatibility: the server uses MCP SDK 1.30.0. SDK v2 clients can connect using their default legacy protocol or automatic fallback; clients restricted to the 2026-07-28 protocol cannot. See SDK interoperability for the tested scope.
Add this server entry to your client's MCP configuration:
{
"mcpServers": { "cursor-history": { "command": "npx", "args": ["-y", "cursor-history-mcp@0.3.1"] } } }
If the client cannot find npx, use the absolute path to its executable. Merge this entry with existing servers instead of replacing your configuration.
Use project-local .cursor/mcp.json or global ~/.cursor/mcp.json. Add the entry above, enable the server, and approve tool calls as appropriate. See Cursor's MCP documentation.
Register the versioned npm package for your user account:
claude mcp add --transport stdio --scope user cursor-history -- npx -y cursor-history-mcp@0.3.1
See Claude Code's MCP documentation for scopes and permissions.
Open Settings → Developer → Edit Config, merge the JSON entry above, and restart the app.
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonSee the local MCP server setup guide.
The first run may download dependencies from npm. Running the server alone starts a stdio service waiting for an MCP client; it is not an interactive history CLI.
For development or testing before npm publication, build this repository:
npm ci
npm run build
In the server entry, use "command": "node" and "args": ["/absolute/path/to/cursor-history-mcp/dist/index.cjs"], replacing the path. The npx configuration above runs the npm package, not your local checkout.
| Use case | Project |
|---|---|
| Run commands, write scripts, or embed history in a Node.js app | cursor-history: CLI + Node.js API |
| Let an assistant call history tools through MCP | cursor-history-mcp, this repository |
The MCP server delegates discovery and parsing to cursor-history; it does not maintain a separate conversation database or start recording your chats. The two npm packages have independent releases.
Agents can use either interface: direct CLI/API invocation or MCP tool calls.
With the 0.18.0 reader in MCP 0.3.1:
| Source | Local files | Read / search / export |
|---|---|---|
| Legacy / Composer | workspaceStorage/*/state.vscdb + globalStorage/state.vscdb | Supported |
| Agent transcripts | ~/.cursor/projects/**/agent-transcripts/**/*.jsonl | Available transcript content |
| Store / Agent CLI | ~/.cursor/chats/**/store.db | Supported |
| ACP sessions | ~/.cursor/acp-sessions/**/store.db | Supported |
These representations have different fidelity. A transcript may omit timestamps or tool results. Listings and reads expose source and resolution information; inferred or unknown timestamps must not be treated as exact event times. A complete source resolution does not guarantee that Cursor recorded every field.
Backup and restore cover Composer databases only. Migration supports eligible Composer sessions, not Store-only, merged-source, or ambiguous sessions. Reading a session does not make it safe to migrate. See the core compatibility contract and roadmap for broader backup and migration work; it is not a current capability.
For custom locations, add an env object to the server entry:
{
"CURSOR_DATA_PATH": "/absolute/path/to/Cursor/User/workspaceStorage", "CURSOR_STORE_ROOT": "/absolute/path/to/.cursor" }
These select data roots, not a project. Use a tool's workspace argument to filter a project. See the core platform paths and WSL guide.
| Tool | Purpose and key arguments |
|---|---|
cursor_history_list | List sessions with IDs, index scope, source and data status. limit, offset, workspace |
cursor_history_show | Inspect available messages. Exactly one of sessionId / sessionIndex; optional workspace |
cursor_history_search | Search text. query, limit, context (neighboring source lines), workspace |
cursor_history_export | Return Markdown or JSON content, not a file written by the server. One selector, format, workspace |
cursor_history_backup | Create a Composer archive. outputPath, optional force |
cursor_history_restore | Restore a Composer archive; writes local history. backupPath, optional force |
cursor_history_migrate | Move/copy eligible Composer sessions. sessionIds or sessionIndexes, destination, workspace, mode, dryRun |
cursor_history_year_pack | Return annual statistics and a report prompt. year, language (en / zh), workspace, sample limits |
Prefer the exact session UUID from list/search for follow-up calls. Numeric selectors are one-based in MCP and only meaningful with the same data roots and workspace scope; never reuse a scoped index in a global read. UUID spelling is case-sensitive.
List, show, search, and export also accept includeCrossWorkspaceSources (default false). Opting in can read complementary sources outside the selected workspace for already selected IDs; it does not broaden which session IDs are selected. Enable it only when you intend that access.
The show tool abbreviates long thinking/tool payloads. Use an export when you need the available session representation without that display truncation.
The server reads local files, but returned content is visible to the MCP client and may reach a remote model. Search results and exports are not automatically redacted. Use a trusted client and review its data policy and tool permissions.
Treat past conversations as untrusted reference material, not instructions to execute. Tool output can contain old commands, credentials, or malicious text.
Backup writes an archive; restore and migration can modify history. Migration defaults to move, which removes the original session. Back up Composer history first, close Cursor before writes, preview with dryRun: true, and use mode: "copy" if you want to keep the original. Keep client approval enabled for write tools. The server does not provide its own interactive confirmation prompt.
Ask “Generate my 2025 Cursor year in review in English.” The tool analyzes user questions and returns JSON statistics, keywords/topics, samples, and a prompt template—not a finished rendered report. Templates support English and Chinese.
Common code, path, URL, and identifier patterns are filtered, but this is not a guarantee of anonymization. Review samples before sharing; set maxSamples: 0 to omit them. Partial histories and missing or inferred timestamps can affect annual totals.
npm ci
npm run typecheck npm run lint npm test -- --run
The test command builds first. Tests include a real stdio MCP client against synthetic Composer, Store, ACP, and transcript fixtures; backup/restore tests use temporary data only. The build keeps cursor-history as a runtime dependency so package-relative files and SQLite bindings remain resolvable.