Skip to main content
Glama
Sign In
callimachus

callimachus

by BetaBots-LLC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to callimachus

No user-submitted related servers found.

    Related Servers

    • brain

      Dakirchik
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search a single local SQLite full-text index of past Claude Code and Codex sessions, Obsidian notes and attachments, GitHub activity, and imported Claude/ChatGPT chats, plus project timelines and recent items. It also lets one agent hand off a session briefing to another so work can continue in a different tool without re-explaining context.
      MIT

    • Memory MCP

      nerdyaustin
      A
      license
      A
      quality
      D
      maintenance
      Provides persistent cross-session memory and full-text search for AI coding assistants, storing project context, decisions, and preferences while enabling searchable access to conversation history via local SQLite.
      8
      1
      MIT

    • chronicle-mcp

      loerei
      A
      license
      Not graded
      quality
      C
      maintenance
      Indexes and searches agent conversation logs from Antigravity and Cursor workspaces, enabling semantic search, token analysis, and benchmarking over local SQLite storage.
      19 npm
      MIT

    • Conversation Search MCP Server

      cordlesssteve
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables comprehensive search and analysis of Claude Code conversation history using full-text search, optional semantic vector search, and conversation management tools. Provides fast SQLite-based indexing with role-based filtering, project organization, and hybrid search capabilities combining keyword and semantic matching.
      -
    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

    A3.7/5.0

    Scored across 23 tools

    Disambiguation4/5

    The tools divide cleanly by object (threads, decisions, gotchas, TODOs, snapshots, project memory), and descriptions explicitly steer between close pairs like get_thread/get_thread_knowledge and search_threads/search_current_project. However, several recall/answer tools such as ask_history, find_prior_work, and recall_decisions overlap enough that an agent could pick the wrong retrieval path without care.

    Naming Consistency4/5

    Almost all names are snake_case verb_noun (list_tags, get_thread, record_decision, search_threads). A handful use noun or adjective phrases (linked_commits, recent_threads, threads_for_file, project_memory, recurring_issues), but the convention remains readable and predictable.

    Tool Count3/5

    At 23 tools, this sits in the heavy/borderline band for a single server. The memory domain has many facets and each tool has a distinct role, but some retrieval variants could likely be consolidated to reduce selection burden.

    Completeness4/5

    The surface covers the main lifecycle: thread discovery/recap/search, decision and gotcha record/recall/contradiction checks, TODO listing/completion, snapshots, and project memory. Minor gaps exist around explicit deletion/pruning, listing projects, or reviewing flagged facts, but these are not core workflow blockers.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources