Skip to main content
MCP server CX Codex

cursor-history — Claude Code MCP server: features and setup

Connects an assistant to local Cursor chats so it can search conversations, inspect sessions, and produce exports. Useful when you need to recover an earlier fix or decision.

Install into Claude Code · Platform CLI All methods and platforms ↓
claude mcp add cursor-history -- npx -y cursor-history-mcp
Open on GitHub

What cursor-history does

The server exposes local Cursor history to an MCP client. An assistant can search conversation text across workspaces, open matching sessions, and request an export. You don’t need to have used this server when the chats were created.

It requires Node.js 20.x or 22.x–26.x, readable Cursor history on the machine, and a client that can run local stdio MCP servers. The client must launch the server where the history files are stored. Search won’t work if those files aren’t accessible.

For parsing and discovery, it relies on cursor-history rather than keeping its own conversation database. Backup and restore apply to Composer databases only. Agent transcripts can lack timestamps or tool results, so they may not show the full session context.

What it helps with

  • find an earlier fix in Cursor conversations
  • inspect sessions related to a bug
  • request a chat export through MCP
  • back up a Composer database

Example prompts for the agent

  • Search my Cursor history for how we fixed the authentication error before.
  • Open the Cursor sessions about this bug and identify the relevant decisions.
  • Export the Cursor conversation where we discussed project setup.

How to install cursor-history

Platform CLI

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

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about cursor-history

How do I install cursor-history in Claude Code?

Run claude mcp add cursor-history -- npx -y cursor-history-mcp. This registers the server with the MCP client.

What does cursor-history do?

It connects local Cursor chat history to an MCP client, letting an assistant search conversations, inspect sessions, and request exports.

Which Cursor history formats can it read?

It supports Composer history, agent transcripts, Store data, and ACP sessions. Transcripts may omit timestamps or tool results.

Similar MCP servers

All MCP servers for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor