Skip to main content
Glama
ByteAsk

byteask-embedded-docs

Official
by ByteAsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to byteask-embedded-docs

Related Servers

  • Harpyja

    DCSTOLF
    A
    license
    B
    quality
    B
    maintenance
    A precision code-retrieval MCP server for coding agents working in large, legacy, and air-gapped codebases. It returns exact file and line range citations from natural-language queries without requiring the agent to perform blind searches.
    3
    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
  • doc-search by SodaShikenn

    doc-searchofficial

    SodaShikenn
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for hybrid documentation search (keyword + vector) and RAG chat, enabling natural language queries with cited answers from indexed repositories.
    MIT

  • Muninn

    rdnpradipta
    F
    license
    A
    quality
    C
    maintenance
    MCP server for querying a page-citable research knowledge base built from PDFs, with exact filename and page citations.
    6
    -

  • McuBuddy

    cunjun
    A
    license
    C
    quality
    A
    maintenance
    MCP server for AI-assisted MCU and embedded firmware debugging. It connects to real hardware via debug probes, inspects CPU/memory/peripherals, manages Keil builds, and provides structured evidence for fault diagnosis.
    19
    6
    MIT

  • nexla-mcp-doc-qa

    ArundhatiCat
    F
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that exposes grounded, source-attributed question-answering over a collection of PDF documents.
    -
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/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct, non-overlapping purpose: search_docs for searching, get_context for expanding search results, and request_document for adding new documents. No two tools could be confused.

Naming Consistency5/5

All tool names follow a clear verb_noun pattern with underscores (search_docs, get_context, request_document), consistently using imperative verbs and descriptive nouns.

Tool Count5/5

With only 3 tools, the server is well-scoped for its domain. Each tool is essential and justified, covering the primary operations without unnecessary bloat or gaps.

Completeness5/5

The tool set covers the full workflow: searching for information, retrieving full context from search results, and requesting new documents when missing. No obvious gaps for the stated purpose of an embedded docs corpus.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources