Skip to main content
Glama
epicsagas

Alcove

by epicsagas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to Alcove

No user-submitted related servers found.

    Related Servers

    • mcp-context

      ericlimabr
      F
      license
      Not graded
      quality
      D
      maintenance
      Local MCP server that provides semantic search (RAG) over code repositories, enabling AI clients like Claude and Gemini to access project context without manual re-upload.
      -

    • local-Rag

      zongzi-zongzhi
      A
      license
      A
      quality
      D
      maintenance
      A local-first document retrieval MCP server that enables AI coding tools like Codex to search private local documents via semantic search and keyword boost, supporting ingestion of PDF, DOCX, TXT, Markdown, and HTML files.
      7
      MIT

    • codebase-rag-mcp

      sudoriaa
      A
      license
      A
      quality
      C
      maintenance
      A local-first MCP server that indexes code repositories and enables AI assistants to search, fetch, and navigate code using BM25 hybrid retrieval, supporting common languages and tools like Codex and ChatGPT.
      8
      MIT

    • Grounded Code MCP

      michaelalber
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that gives AI coding assistants retrieval access to your personal knowledge base of books, standards, and docs, grounding their answers in sources you trust.
      MIT

    • KnowledgeRail

      Deviank88
      A
      license
      C
      quality
      A
      maintenance
      Local-first MCP server that turns project documentation and source code into durable, evidence-backed context for AI agents, with bounded retrieval and explicit gap reporting.
      8
      318 npm
      Apache 2.0
    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.3/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes (audit vs. validate vs. lint could overlap, but descriptions clarify: audit focuses on missing/outdated, validate on policy, lint on semantic issues). Some overlap exists between search_vault and search_project_docs, but scope separation is clear.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (get_project_docs_overview, search_project_docs, list_projects, configure_project). Minor deviations like 'promote_document' and 'check_doc_changes' are still consistent in style. Slight inconsistency in count (some use 'docs' vs 'document').

    Tool Count5/5

    15 tools is well-scoped for a documentation management server, covering viewing, searching, initialization, configuration, validation, linting, indexing, and vault operations. Each tool serves a clear purpose without feeling excessive.

    Completeness4/5

    Covers the main lifecycle: init (init_project), read (get_doc_file, search_project_docs), update (import via promote_document, rebuild_index), and quality checks (audit, validate, lint). Minor gaps include no direct doc editing/update tool and no delete tool, but agents can use file system tools externally.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources