Cursor History

Name: Cursor History
Author: S2thend

by S2thendversion 0.3.1i★ –iRuns on your computer

Registry nameio.github.S2thend/cursor-history

Install

Overview

Description from the maker (original English)

MCP server for browsing, searching, exporting, and backing up your Cursor AI chat history

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Chat & email

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "cursor-history": {
      "command": "npx",
      "args": [
        "-y",
        "cursor-history-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add cursor-history -- npx -y cursor-history-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "cursor-history": {
      "command": "npx",
      "args": [
        "-y",
        "cursor-history-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "cursor-history": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "cursor-history-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account S2thend, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Chat & emaili

More stars than 0% of the other 1772 servers in this category
Published to the registry more recently than 30% of the other 1772 servers in this category
Basic checks equal to or better than 100% of the other 1772 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Cursor History safe?

It passed 1 of 1 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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago

Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 31 days ago

Install

MCP WhatsApp Cloud

by codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago

Install

README from the maker

Open the README

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.

Cursor History MCP

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

Quick start

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.

Configure the npm package

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.

Cursor

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.

Claude Code

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.

Claude Desktop

Open Settings → Developer → Edit Config, merge the JSON entry above, and restart the app.

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

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

Run from source

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.

Two projects, one history reader

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.

Works across storage generations

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.

Available tools

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.

Try these requests

“Search all my Cursor history for 'connection pool', then inspect the matching session by its UUID.”
“Search only /work/myapp. Keep that workspace scope when opening a result.”
“Export this session as JSON, including the available source details.”
“Preview copying this Composer session to /work/new-app with dryRun. Do not modify anything yet.”

Local data and write safety

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.

MCP-exclusive: Year in Review

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.

Development

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.

Issues · Pull requests · MIT license

Cursor History

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Chat & emaili

Common questions

Alternatives

Vexa

emailmd

MCP WhatsApp Cloud

README from the maker

Cursor History MCP

Quick start

Configure the npm package

Cursor

Claude Code

Claude Desktop

Run from source

Two projects, one history reader

Works across storage generations

Available tools

Try these requests

Local data and write safety

MCP-exclusive: Year in Review

Development