Skip to main content
Glama
Sign In
google-ai-history-mcp

google-ai-history-mcp

by travispflanz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to google-ai-history-mcp

No user-submitted related servers found.

    Related Servers

    • yt-memory

      RC0d3r
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to curate YouTube watch history and locally search selected transcripts using SQLite FTS5, ChromaDB embeddings, and reciprocal rank fusion, with tools to browse unindexed history and add videos.
      MIT

    • google-activity-assistant

      Daemon-Killer
      A
      license
      A
      quality
      D
      maintenance
      MCP server for querying your local Google Takeout activity (Search/YouTube history) via SQLite/FTS5. Provides tools for keyword search, activity stats, and database info, enabling AI assistants to cite your personal history.
      3
      MIT

    • LLMemory MCP Server

      meir-may
      A
      license
      Not graded
      quality
      D
      maintenance
      A remote MCP server that enables AI coding agents to search and retrieve context from imported AI chat history (ChatGPT, Claude, Codex, Claude Code) stored in Google Drive, with zero server-side storage and OAuth-based privacy.
      MIT

    • Session Archive

      CyberArchitecta
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and retrieving ChatGPT and Claude conversation exports locally, allowing assistants to fetch handoff context and continue conversations through read-only MCP tools.
      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

    B3.1/5.0

    Scored across 6 tools

    Disambiguation3/5

    The three ingestion tools (import from files, sync from browser, fetch from URL) are distinguished by their source, and the descriptions do explain the differences. However, get_google_ai_chat explicitly accepts a 'direct URL' while fetch_google_ai_chat_url also pulls a chat by URL, creating a genuine overlap that could cause misselection.

    Naming Consistency4/5

    All tools use snake_case with a verb_noun pattern (import_*, sync_*, list_*, search_*, get_*, fetch_*). The two ingestion names are unusually long and tack on qualifiers ('_or_files', '_from_browser'), but the convention itself is readable and consistent.

    Tool Count4/5

    Six tools is a reasonable scope for a chat-archive server covering ingest, list, search, and retrieve. Nothing feels redundant in count, though the two URL/file ingestion paths could arguably be folded into fewer tools.

    Completeness4/5

    The ingestion-plus-retrieval lifecycle is well covered: import, sync, list, search, get, fetch. There are no delete, export, or tagging/metadata operations, but these are minor gaps an agent can work around outside the server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources