Skip to main content
Glama
cursor-history-mcp

cursor-history-mcp

by S2thend

Cursor History MCP

npm version npm downloads License: MIT Node.js

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

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.

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.

Related MCP server: conversation-history-mcp

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

Available Tools

8 tools
cursor_history_backupA

Back up Composer chat history to a restorable ZIP archive. Store databases, Agent transcripts and ACP stores are not included.

Inputs: force, outputPath.

cursor_history_exportB

Export a Cursor AI chat session to Markdown or JSON format. Returns the formatted content.

Inputs: format, sessionId, workspace, sessionIndex, +1 more.

cursor_history_listB

List Cursor AI chat sessions. Returns recent sessions with metadata including workspace, message count, and timestamps.

Inputs: limit, offset, workspace, includeCrossWorkspaceSources.

cursor_history_migrateA

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.

Inputs: destination (required), mode, dryRun, workspace, +2 more.

cursor_history_restoreA

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

Inputs: backupPath (required), force.

cursor_history_showA

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.

Inputs: sessionId, workspace, sessionIndex, includeCrossWorkspaceSources.

cursor_history_year_packA

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.

Inputs: year, language, workspace, maxSamples, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: backup/restore handle archiving, list/show/search/export handle viewing and retrieval, migrate handles workspace transfer, and year_pack generates summaries. There is no meaningful overlap between any two tools.

    Naming Consistency4/5

    All tools share the snake_case `cursor_history_` prefix followed by an action verb (backup, list, show, search, export, restore, migrate). The one minor deviation is `cursor_history_year_pack`, which uses a noun-ish suffix rather than a verb, slightly breaking the established pattern.

    Tool Count5/5

    Eight tools is a well-scoped count for a history-management server. Each tool covers a distinct aspect of the domain—backup, restore, list, inspect, search, export, migrate, and summaries—without unnecessary bloat or missing essentials.

    Completeness5/5

    The tool set covers the full lifecycle of Cursor chat history: backing up, restoring, listing, inspecting, searching, exporting, migrating, and generating year-in-review packages. No obvious gaps exist for the stated purpose; destructive operations like deleting individual sessions are reasonably omitted.

    Maintenance

    ActivityStale
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A powerful MCP server that extracts, stores, searches, and analyzes Claude.ai conversations with SQLite database, semantic search, and multiple export formats including Obsidian and PDF.
      97 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Capture, index, and search your Claude Code conversation history. Provides an MCP server for Claude Code to query its own past conversations.
      1
      MIT