Skip to main content
Glama
DestinyJazz

claude-web-history-mcp

by DestinyJazz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to claude-web-history-mcp

No user-submitted related servers found.

    Related Servers

    • context-bridge

      zachvp
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to search and retrieve past chat history from Claude.ai exports and Claude Code sessions, allowing the AI to reference previous conversations and decisions.
      MIT

    • ccfolio

      Hippensteel
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching and browsing past Claude Code conversations directly from within an active Claude session, with full-text search and cost tracking.
      MIT

    • mcp-server-chat-history

      ilovecat1005
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to full-text search, list, and read your exported ChatGPT and Claude conversations from a local conversations.json file, running locally with read-only file access and no network requests. Supports both official export formats with automatic detection.
      MIT

    • hist-bridge

      maqitong
      A
      license
      A
      quality
      C
      maintenance
      Enables listing and continuing conversations from Claude Code, Codex, Cursor, and GLM, allowing context handoff between tools by providing historical transcripts as context.
      5
      MIT

    • claude-session-export

      coreyx
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code sessions to list projects and sessions and export session transcripts to readable text files, including its own or another project's history.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are mostly distinct: debug_connection checks credentials, list_web_conversations lists metadata, read_web_conversation fetches content, and save_web_conversation persists to disk. The only potential overlap is read vs save, but the descriptions clarify the output destination (context vs file).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: debug_connection, list_web_conversations, read_web_conversation, save_web_conversation. The singular/plural variation is natural and doesn't create confusion.

    Tool Count5/5

    With only 4 tools, the set is tightly scoped to the server's purpose of accessing and persisting claude.ai web conversations. Each tool serves a clear, non-redundant function, and the small count is appropriate for the niche domain.

    Completeness4/5

    The core lifecycle is covered: list conversations, read a conversation, and save a conversation. Debugging is supported via debug_connection. The only potential gaps are search or deletion, but those are arguably outside the intended scope of a history-retrieval tool.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources