Skip to main content
Glama
Sign In
cursor-history-mcp

cursor-history-mcp

by S2thend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to cursor-history-mcp

No user-submitted related servers found.

    Related Servers

    • Cairn

      veax-project
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that backs up and syncs Claude Code conversations across accounts, and lets Claude search your complete history via natural language.
      GPL 3.0

    • memex

      dioniipereyraa
      A
      license
      A
      quality
      D
      maintenance
      MCP server that indexes Claude.ai chats and local Claude Code sessions, enabling semantic and keyword search across all your conversations with Claude.
      6
      5
      MIT

    • Quaid

      SEEDO-Media-Ltd
      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.
      2 npm
      1
      MIT

    • MCP Claude Context Server

      hamzaamjad
      A
      license
      Not graded
      quality
      C
      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.
      60 PyPI
      1
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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
    ResponsivenessNo recent community issues

    Resources