Cursor History MCP server

by S2thend·io.github.S2thend/cursor-history·v0.3.1·33 stars

No reviews yet

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

B80/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B80/100

full report

Adoption

Growing

33 stars64 downloads/wk

Reviews

Write one

Nobody has reviewed Cursor History yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cursor History tools (8)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

cursor_history_backup
Back up Composer chat history to a restorable ZIP archive. Store databases, Agent transcripts and ACP stores are not included.
cursor_history_export
Export a Cursor AI chat session to Markdown or JSON format. Returns the formatted content.
cursor_history_list
List Cursor AI chat sessions. Returns recent sessions with metadata including workspace, message count, and timestamps.
cursor_history_migrate
Move or copy eligible Composer sessions between workspaces. Store-only, merged-source and ambiguous sessions are refused. Use dryRun to preview. Moving removes the original; back up first.
cursor_history_restore
\u26A0\uFE0F DESTRUCTIVE: Restore Composer databases from a backup archive. This can overwrite Composer history; it does not restore Store databases, Agent transcripts or ACP stores. Back up current Composer data first.
cursor_history_search
Search across all Cursor AI chat sessions for a keyword or phrase. Returns matching sessions with context around each match.
cursor_history_show
Inspect the available messages and tool activity in a Cursor session, with source and timestamp provenance. Long thinking and tool payloads are abbreviated; use export for unabridged available content.
cursor_history_year_pack
Generate a year-in-review data package from Cursor AI chat history. Produces a sanitized JSON summary with statistics, topics, and keywords, plus a prompt template for LLM-based report generation. Read-only operation.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

1 medium

Code scan2 source files scanned20/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 37 days ago12/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

mediumeval / new Function usedexec.eval

dist/index.cjs: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…

Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Cursor History compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 80/100; higher than 60% of 48,243 servers
Tools: 8; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 33; more than 92% of 28,706 servers
Downloads a week: 64; more than 50% of 12,306 servers with a package

What its tools let an agent do: 8 read

Install Cursor History in Claude Code, Cursor or VS Code

Runs npx -y cursor-history-mcp on your machine. Read the scan report first; the gateway never runs local packages.

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

Add to Cursor

What the publisher says

From the Cursor History repository's README, as published. We do not edit it. Read it on GitHub

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

2026-10-15downgradeA → Bscore 80: eval / new Function used

Cursor History: common questions

Is Cursor History MCP server safe?: Mostly: it is graded B (80/100). Read the Cursor History safety report
How do I install Cursor History?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Cursor History need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Cursor History maintained?: The last commit was 58 days ago (2026-09-08). The latest release is v0.3.1.
How does Cursor History compare with other MCP servers?: safety score 80/100 (higher than 60% of 48,243 servers); tools 8 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.