embedded-docs

Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references.

    How to connect

    How to connect embedded-docs to Claude

    The server address to paste into Claude settings:

    https://mcp.byteask.ai/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect embedded-docs to ChatGPT

    The server address to paste into ChatGPT settings:

    https://mcp.byteask.ai/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect embedded-docs to Cursor

    The server address to paste into Cursor settings:

    https://mcp.byteask.ai/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (3)

    Raw names from tools/list. Only developers need these.

    search_docsSearch the indexed embedded / firmware / hardware reference corpus; return verbatim, page-cited evidence. The indexed corpus covers: grid-interconnection & DER standards (IEEE 1547 / 1547.1 / 2030.5, SunSpec Modbus profiles, ENA G98/G99 and other grid codes); industrial & fieldbus protocols (Modbus, CAN / ISO-TP, MQTT); SCPI instrument-programming manuals (power analysers, grid simulators, programmable AC sources); Arm Cortex-M and other MCU / hardware datasheets (registers, bitfields, reset values); FPGA transceivers, silicon & toolchain (AMD/Xilinx UltraScale GTH/GTY/GTM and 7-series GTX, SelectIO/clocking, Vivado & Vitis HLS, device datasheets) plus networking & interface IP product guides (10G/25G and 100G Ethernet, PCIe integrated block, XDMA/QDMA/AXI-DMA, DDR4 memory IP); bus & interconnect specs (AMBA AXI and AXI4-Stream); optical-module management (SFF-8472/8636 SFP+/QSFP DDM); networking protocol RFCs (IPv4, TCP, UDP, ARP, Internet checksum), the PCIe Base Specification and IEEE 1588 PTP; exchange market-data & order-entry protocols (Nasdaq TotalView-ITCH & OUCH, NYSE Pillar, CME MDP/SBE, Cboe PITCH/BOE, FIX); safety-critical C/C++ coding guidelines and language standards (AUTOSAR C++14, C++ Core Guidelines, MISRA C:2012, the ISO C++ working draft, C11); and embedded library / API references. Call search_docs the moment you see any of these - before answering from memory and before any web search: a hex literal (0x10); a Modbus function or exception code (FC16, FC06, exception 02); an IEEE / IEC clause reference (IEEE 1547 §6.4.1); a SCPI command verb (*IDN?, :MEAS:VOLT?); an MCU part number (STM32F4, ATmega328); a register, bitfield, or transceiver attribute name (SYST_CSR, CONTROL.SPSEL, RXBUF_EN, RXCDR_CFG); a Xilinx/AMD document ID (UG576, PG213, DS922); an AMBA AXI / AXI4-Stream signal or response code (TVALID, TKEEP, BRESP/DECERR); a PCIe TLP or DMA descriptor field; an exchange message or field (ITCH Add Order, FIX Tag 35, SBE templateId, PITCH); an
    get_contextExpand a previous search hit to its full verbatim section (markdown). Args: result_id: The result_id from a search_docs hit. effort: Internal diagnostics tag; clients should leave this unset.
    request_documentRequest that a document be ADDED to the corpus - use this when search_docs returns 'no confident match' for material it should cover (a standard, protocol spec, SCPI or instrument manual, MCU / hardware datasheet, or library reference). This does NOT search; use search_docs for that. Pass ONE string with as much as you know: the document title or standard number, a URL if you have one, the edition / version, and what you were looking for. Requests are reviewed and the document is typically added within 24 hours.