Skip to main content
Glama
anands-bounteous

historical-kb-mcp

by anands-bounteous
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to historical-kb-mcp

No user-submitted related servers found.

    Related Servers

    • triage-mcp

      architect-34
      A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to triage GitHub issues by retrieving similar reported issues and classifying components using historical data.
      6
      MIT

    • Context Graph MCP Server

      ingpoc
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables storing, querying, and managing decision traces with semantic search using Voyage AI embeddings and ChromaDB. Supports outcome tracking and category filtering for software development decisions.
      -

    • cheq-tickets

      GalDaich
      A
      license
      A
      quality
      C
      maintenance
      Enables semantic search and analysis of customer support tickets. Provides tools to search tickets, analyze the dataset, and retrieve individual tickets using natural language.
      3
      MIT

    • AI Agent History RAG MCP

      velenzaboc
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent, searchable memory across AI coding agent and chat history (Claude Code, Codex, Gemini CLI, ChatGPT, and more) via retrieval-augmented generation, enabling semantic and hybrid search to retain context across sessions.
      5
      MIT

    • Memory-MCP

      wb200
      A
      license
      A
      quality
      D
      maintenance
      Provides persistent memory for AI agents using hybrid search (vector embeddings + BM25) with neural reranking, enabling storage and retrieval of insights, debugging solutions, and patterns across coding sessions.
      8
      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

    A3.8/5.0

    Scored across 7 tools

    Disambiguation3/5

    Most tools are clearly distinct: get_analysis, list_analyses, search_similar, delete_analysis, and get_kb_stats each serve different purposes. However, store_analysis and update_analysis overlap because store_analysis is an upsert that merges fields into existing records, making the boundary between creating and updating ambiguous.

    Naming Consistency4/5

    The naming is predominantly verb-first and predictable: store_, get_, update_, list_, delete_, search_, get_. Minor deviations include list_analyses being plural while other resource tools are singular, search_similar lacking a direct object, and get_kb_stats using an abbreviation instead of a full noun.

    Tool Count5/5

    Seven tools is well-scoped for a knowledge-base server: full CRUD plus specialized search and statistics. Each tool earns its place, and the count is neither too thin nor excessively heavy.

    Completeness5/5

    The surface covers the full lifecycle of analysis records: create via store_analysis, read via get_analysis, update via update_analysis, delete via delete_analysis, and browse via list_analyses. The additional search_similar and get_kb_stats tools round out the domain without leaving obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources