cursor-history-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cursor_history_listB | List Cursor AI chat sessions. Returns recent sessions with metadata including workspace, message count, and timestamps. |
| 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. |
| cursor_history_searchA | Search across all Cursor AI chat sessions for a keyword or phrase. Returns matching sessions with context around each match. |
| cursor_history_exportB | Export a Cursor AI chat session to Markdown or JSON format. Returns the formatted content. |
| cursor_history_backupA | Back up Composer chat history to a restorable ZIP archive. Store databases, Agent transcripts and ACP stores are not included. |
| 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. |
| 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. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.