Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.S2thend/cursor-history

NPM · CURSOR-HISTORY-MCP · SCANNED SEP 20

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

Available components

+6 this week 94 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 60 of 145 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to S2thend/cursor-history-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 11 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1047 tokens (~130/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.S2thend/cursor-history MCP server?

io.github.S2thend/cursor-history runs locally as an npm package, launched with npx -y cursor-history-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · cursor-history-mcp

# add to Claude Code
claude mcp add s2thend-cursor-history -- npx -y cursor-history-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "s2thend-cursor-history": {
      "command": "npx",
      "args": [
        "-y",
        "cursor-history-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "s2thend-cursor-history": {
      "command": "npx",
      "args": [
        "-y",
        "cursor-history-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add s2thend-cursor-history -- npx -y cursor-history-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "s2thend-cursor-history": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "cursor-history-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add s2thend-cursor-history --command npx --arg -y --arg cursor-history-mcp
# ~/.hermes/config.yaml
mcp_servers:
  s2thend-cursor-history:
    command: "npx"
    args: ["-y", "cursor-history-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "s2thend-cursor-history": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "cursor-history-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add s2thend-cursor-history -t stdio -c npx -a -y cursor-history-mcp
// mcp.json
{
  "mcpServers": {
    "s2thend-cursor-history": {
      "command": "npx",
      "args": [
        "-y",
        "cursor-history-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +6
    • Source repository: fail → pass security
    • Package version: 0.2.4 → 0.3.1 functional
  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 −5
    • Source repository: pass → fail security
    • Security disclosure: fail → unverified functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/cursor-history-mcp@0.3.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo S2thend/cursor-history-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/S2thend/cursor-history-mcp/.github/workflows/publish.yml@refs/tags/v0.3.1
Rekor log index 2763112076
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:6935f84d11e49afffbc10f173216d5f6ab0ec9d7ef6365cb9383a0dcf7ad1817177b32cfdf608818beeb18d3e4432a8206b0a8d4b418bf95d86cb6c9f

Background: How many MCP packages publish verified provenance →

Dependencies 145 packages
Packages resolved 145
Deprecated 1
Stale 59
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,047 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cursor_history_backup ~84

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

NameTypeReqDescription
forcebooleanOverwrite existing backup file if it exists (default: false)
outputPathstringPath where the backup file should be saved. If not specified, saves to ~/cursor-history-backups/ with a timestamp.

No output schema declared.

No examples provided.

cursor_history_export ~148

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

NameTypeReqDescription
formatstringExport format: 'markdown' for human-readable, 'json' for structured data
includeCrossWorkspaceSourcesbooleanOpt in to complementary sources outside this workspace, only for already selected session IDs. Default: false.
sessionIdstringExact native session UUID returned by list/search. Case-sensitive; do not normalize.
sessionIndexintegerOne-based index from a list with the same workspace scope. Prefer sessionId for reuse.
workspacestringWorkspace path. Reuse the same scope for listing and reading a session index.

No output schema declared.

No examples provided.

cursor_history_list ~123

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

NameTypeReqDescription
includeCrossWorkspaceSourcesbooleanOpt in to complementary sources outside this workspace, only for already selected session IDs. Default: false.
limitintegerMaximum number of sessions to return (default: 20, max: 1000)
offsetintegerNumber of sessions to skip for pagination (default: 0)
workspacestringWorkspace path. Reuse the same scope for listing and reading a session index.

No output schema declared.

No examples provided.

cursor_history_migrate ~164

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.

NameTypeReqDescription
destinationstringyesAbsolute path to the destination workspace folder
dryRunbooleanPreview without changing history (default: false).
modestringMigration mode: 'move' deletes original, 'copy' keeps original
sessionIdsarrayExact native UUIDs from list/search. Use instead of sessionIndexes for stable selection.
sessionIndexesarrayList of session indexes to migrate (1-based, as shown in list output)
workspacestringSource workspace scope; use the same scope that produced the session indexes.

No output schema declared.

No examples provided.

cursor_history_restore ~96

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

NameTypeReqDescription
backupPathstringyesPath to the backup file to restore from
forcebooleanAllow overwriting existing backup targets (default: false). The server has no interactive confirmation; obtain approval in the client.

No output schema declared.

No examples provided.

cursor_history_search ~138

Search across all Cursor AI chat sessions for a keyword or phrase. Returns matching sessions with context around each match.

NameTypeReqDescription
contextintegerNumber of source lines of context requested around each match (default: 50)
includeCrossWorkspaceSourcesbooleanOpt in to complementary sources outside this workspace, only for already selected session IDs. Default: false.
limitintegerMaximum number of results to return (default: 10)
querystringyesThe search query (keyword or phrase to find)
workspacestringWorkspace path. Reuse the same scope for listing and reading a session index.

No output schema declared.

No examples provided.

cursor_history_show ~145

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.

NameTypeReqDescription
includeCrossWorkspaceSourcesbooleanOpt in to complementary sources outside this workspace, only for already selected session IDs. Default: false.
sessionIdstringExact native session UUID returned by list/search. Case-sensitive; do not normalize.
sessionIndexintegerOne-based index from a list with the same workspace scope. Prefer sessionId for reuse.
workspacestringWorkspace path. Reuse the same scope for listing and reading a session index.

No output schema declared.

No examples provided.

cursor_history_year_pack ~149

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.

NameTypeReqDescription
languagestringReport language preference (default: en)
maxSampleLengthintegerMaximum characters per sample (default: 120)
maxSamplesintegerMaximum sample questions to include (default: 30)
topicsCountintegerNumber of topics to extract (default: 7)
workspacestringOptional workspace path to filter sessions
yearintegerCalendar year to analyze (default: current year)

No output schema declared.

No examples provided.

Common questions

What is the io.github.S2thend/cursor-history MCP server?

io.github.S2thend/cursor-history is an MCP server listed in the public MCP registry as io.github.S2thend/cursor-history. MCP server for browsing, searching, exporting, and backing up your Cursor AI chat history. This page covers its npm package (cursor-history-mcp).

Is the io.github.S2thend/cursor-history MCP server safe to use?

io.github.S2thend/cursor-history scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.S2thend/cursor-history MCP server expose?

io.github.S2thend/cursor-history exposes 8 tools: cursor_history_list, cursor_history_show, cursor_history_search, cursor_history_export, cursor_history_backup, and 3 more. Their descriptions and schemas cost roughly 1,047 tokens of context every time the server is loaded.

Is the io.github.S2thend/cursor-history MCP server still maintained?

io.github.S2thend/cursor-history is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.S2thend/cursor-history MCP server under?

io.github.S2thend/cursor-history declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.