Skip to main content
Glama
RobHudson72

flightlog

by RobHudson72
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to flightlog

No user-submitted related servers found.

    Related Servers

    • Quaid

      SEEDO-Media-Ltd
      A
      license
      Not graded
      quality
      B
      maintenance
      Capture, index, and search your Claude Code conversation history. Provides an MCP server for Claude Code to query its own past conversations.
      6 npm
      1
      MIT

    • ClaudeHistoryMCP

      jhammant
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that makes Claude Code conversation history searchable and proactively useful by indexing past sessions with hybrid BM25+TF-IDF search, extracting decisions and solutions, and auto-injecting relevant project context at session start.
      9
      6 npm
      66
      MIT

    • engram-mcp

      lowbridgee
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables semantic and keyword search over Claude Code conversation history stored locally, using hybrid search, local embeddings, and time-decay scoring.
      10 npm
      MIT

    • memex

      dioniipereyraa
      A
      license
      A
      quality
      B
      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
      6
      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/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: delete sessions, get full transcript, trigger re-indexing, check status, list sessions, rebuild index, search conversations, show stats, sync to remote, tail recent messages. No functional overlap.

    Naming Consistency4/5

    All tools use the 'flightlog_' prefix and most follow a verb_noun pattern (e.g., delete_sessions, get_session, list_sessions, ingest_status). A few are just verbs (ingest, rebuild, search, stats, sync, tail) without a noun, which is a minor inconsistency but still clear.

    Tool Count5/5

    10 tools is well-scoped for a logging/observability server. Each tool serves a necessary function—ingestion, search, retrieval, deletion, syncing, statistics—without redundancy or bloat.

    Completeness5/5

    The tool set covers the full lifecycle: ingestion (flightlog_ingest), browsing (flightlog_list_sessions), searching (flightlog_search), reading (flightlog_get_session, flightlog_tail), deleting (flightlog_delete_sessions), rebuilding (flightlog_rebuild), syncing (flightlog_sync), and status/stats (flightlog_ingest_status, flightlog_stats). No obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources