Skip to main content
Glama
MicroMichaelIE

mcp-copilotcli-history

by MicroMichaelIE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to mcp-copilotcli-history

No user-submitted related servers found.

    Related Servers

    • Cursor DB MCP Server

      TaylorChen
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying, searching, and analyzing Cursor IDE conversation history from SQLite workspaceStorage databases. Supports exporting chat data in multiple formats and provides workspace utilities for managing conversation data across projects.
      MIT

    • MCP Memory

      PascalNoisette
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Kilo Code and Opencode conversation history stored in a local SQLite database, allowing users to list projects and sessions, read messages, and perform full-text keyword searches across all messages.
      -

    • ai-history

      Bluscream
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching, indexing, and recovering past AI chat sessions and agent actions from local AI coding tools, with optional vector database semantic search and direct filesystem access.
      -

    • chatlab-mcp

      gamesme
      F
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to query local ChatLab chat history using natural language, with tools for session listing, message retrieval, and analytics.
      17
      10 npm
      -

    • thimiko

      azerv1
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and retrieving local chat history from Codex and Claude CLI sessions via BM25 full-text search and MCP tools.
      2
      MIT
    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 6 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of session history: retrieval, statistics, listing, and various search types (by file path, full-text, tool usage). There is no overlap in functionality.

    Naming Consistency5/5

    All tools use snake_case with a consistent verb_noun pattern (e.g., get_session_conversation, search_by_file_path). The naming is predictable and intuitive.

    Tool Count5/5

    6 tools is an ideal size for a focused history server. It covers all core operations without being overwhelming or insufficient.

    Completeness4/5

    The tool set covers browsing, listing, and searching sessions comprehensively. Minor gaps exist: there is no tool to delete or export session history, which might be expected for a history management utility.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources