Embedded Docs MCP Server

by byteask Your server? Claim it

answering

Embedded Docs is answering right now. Last checked 8 min ago. It exposes 3 tools. Last commit 20 Jun 2026.

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

Uptime history 52 days of history · worst day 91%

52 days agonow

87.9%

Uptime 24h

80 of 91 checks

Tools

read from the server

581 ms

Response time

average over 24h

Stars

last commit 20 Jun 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 20 September 2026. No other catalogue keeps this.

20 Sep a tool description was rewritten get_context

What the code does

We read the source, 14 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command assets/make_demo_gif.py:303

        subprocess.run(["ffmpeg", "-y", "-v", "error", "-i", os.path.join(tmp, "f%04d.png"),

Builds a file path from a variable assets/make_demo_gif.py:301

            frame(i / FPS * 1000).save(os.path.join(tmp, f"f{i:04d}.png"))

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add embedded-docs --transport http https://mcp.byteask.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "embedded-docs": {
      "url": "https://mcp.byteask.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.embedded-docs]
url = "https://mcp.byteask.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "embedded-docs": {
      "url": "https://mcp.byteask.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "embedded-docs": {
      "url": "https://mcp.byteask.ai/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

context

get_context

Expand a previous search hit to its full verbatim section (markdown). Args: result_id: The id from a search_docs hit's `_ref:` line - the token inside the backticks, e.g. E1_Nasdaq_ITCH-5.0:1.2:1:0. Pass it exactly. effort: Internal diagnostics tag; clients should leave this unset.

docs

search_docs

Search 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 SFP/QSFP diagnostic byte; a coding-guideline rule ID (AUTOSAR Rule A0-1-1 / M0-1-2, Core Guidelines P.1 / ES.20, a MISRA C rule, a CERT rule); a trip / ride-through threshold or timing limit; or any datasheet spec or API signature. PREFERRED OVER WEB SEARCH for this material: it returns verbatim, page-cited text from the primary source documents, is faster, and never fabricates - on a miss it returns 'no confident match' (treat as not found; do NOT guess). Cheap and safe to call several times per task.

request

request_document

Request 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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.byteask.ai/mcp	streamable-http	answering	603 ms	8 min ago

Alternatives to Embedded Docs

same job, measured the same way

rmbr

by srock44

Embedded, local-first memory and retrieval for AI agents. One SQLite file, no server, no API key.

130 installs/wk local only

Library

by siftdex

Verified doc corpora for agents: grep-first retrieval, hashed pages, Merkle+RFC-3161 receipts

13 tools answering

Qiskit Documentation MCP Server

by qiskit

MCP server for querying and retrieving Qiskit documentation, guides, and API references

131 installs/wk local only

RTFM

by roomi-fields

The open retrieval layer for AI agents — index code, docs, data. Search via MCP.

9 734 installs/wk local only

Okfshare MCP

by megapanchamz

Shared, versioned knowledge for AI coding agents: cited retrieval and publishing of OKF bundles.

24 installs/wk local only

Ragie

by mcparmory

Ingest, manage, and retrieve documents for RAG-powered AI applications

261 installs/wk local only

Moxie Docs

by jackalope-dev

Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.

12 tools answering

CUDA-Q Docs

by rogerawong

CUDA-Q docs, API reference, and runnable examples for AI agents, pinned to your installed version.

259 installs/wk local only

Embedded Docs — questions

Answers built from our own checks of this server.

What can Embedded Docs do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_context, request_document, search_docs. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Embedded Docs working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 80 of 91 checks got a reply (87.9%), average response time 581 ms. The bar chart above shows every period we have measured.

How do I connect Embedded Docs?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Embedded Docs need an API key?

No. Embedded Docs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Embedded Docs?

It answers our handshake in 581 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Embedded Docs open source?

Yes — it is published under the MIT licence, written in Python, 24 stars on GitHub and 2 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.