Cursor History MCP Server

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

Local serverstdioPython

What is the Cursor History MCP MCP server?

MCP server for browsing, searching, and exporting Cursor AI chat history. Exposed over MCP by the cursor history mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Bring your Cursor AI chat history directly into Claude. Search past conversations, export sessions, create backups, and generate year-in-review reports—all through natural language. Built on the Model Context Protocol for seamless AI assistant integration.

Its toolset

Everything the assistant can do here goes through one of these:

  • cursor_history_list — List chat sessions with metadata
  • cursor_history_show — View full conversation content
  • cursor_history_search — Search across all sessions
  • cursor_history_export — Export session to Markdown or JSON
  • cursor_history_backup — Create backup of all history
  • cursor_history_restore — Restore from backup (destructive)
  • cursor_history_migrate — Move/copy sessions between workspaces (destructive)
  • cursor_history_year_pack — Generate year-in-review data package with stats, topics, and prompt template
  • Cursor — The Cursor tool exposed by this server

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at cursor-history-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

  • Node.js 20+ - Cursor IDE installed with existing chat history

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cursor History MCP's toolset — cursor_history_list, cursor_history_show, cursor_history_search and 6 more — is a fair guide to whether it matches your workflow. It is maintained by s2thend; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cursor History MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Cursor History MCP.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the cursor history mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
cursor_history_listList chat sessions with metadata
cursor_history_showView full conversation content
cursor_history_searchSearch across all sessions
cursor_history_exportExport session to Markdown or JSON
cursor_history_backupCreate backup of all history
cursor_history_restoreRestore from backup (destructive)
cursor_history_migrateMove/copy sessions between workspaces (destructive)
cursor_history_year_packGenerate year-in-review data package with stats, topics, and prompt template
CursorThe Cursor tool exposed by this server.

How to install the Cursor History MCP MCP server

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

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js 20+ - Cursor IDE installed with existing chat history

Example prompts to try

  • Use Cursor History MCP to cursor history list.
  • Use Cursor History MCP to cursor history show.
  • Use Cursor History MCP to cursor history search.

Frequently asked questions

It connects Cursor History MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (cursor_history_list, cursor_history_show, cursor_history_search, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Cursor History MCP directly.