byteaskai
# ByteAsk Embedded Docs MCP Page-cited retrieval over embedded systems documentation, datasheets, reference manuals, RTOS documentation, coding standards, and firmware engineering references for AI coding agents. **Registry Namespace:** `ai.byteask/embedded-docs` **Endpoint:** `https://mcp.byteask.ai/mcp` **Documentation:** https://docs.byteask.ai/embedded **GitHub:** https://github.com/ByteAsk/ByteAsk-Embedded-MCP --- # Why This MCP Exists Modern AI coding agents are excellent at generating code, but often struggle when working with vendor-specific embedded documentation, hardware reference manuals, firmware SDKs, and coding standards. Embedded engineers routinely need answers from: * STM32 Reference Manuals * ARM Cortex-M Technical Reference Manuals * CMSIS Documentation * FreeRTOS Documentation * Zephyr Documentation * ESP-IDF Documentation * Nordic SDK Documentation * NXP Documentation * MISRA C * MISRA C++ * AUTOSAR * Device Datasheets * Vendor Application Notes Searching these sources manually can require navigating hundreds or thousands of pages of documentation. ByteAsk Embedded Docs MCP gives AI coding agents direct access to these references and returns page-cited answers grounded in source documentation. --- # Features ## Page-Cited Retrieval Every answer is grounded in source documentation with citations to the original reference. This enables engineers to verify claims directly against vendor documentation. --- ## Documentation Search Search across embedded and firmware engineering references. Examples: * Peripheral configuration * Register descriptions * DMA setup * Interrupt handling * Clock configuration * RTOS APIs * MISRA compliance questions * ARM architecture details --- ## Agent-Native Works directly with MCP-compatible tools including: * Claude Code * Claude Desktop * Cursor * Windsurf * VS Code MCP Clients * GitHub Copilot MCP * Any MCP-compatible agent --- ## Remote Hosted No indexing, crawling, or local setup req
https://byteaskai.run.tools
How to connect
-
Smithery (hosted)
1. Open https://smithery.ai/servers/kulkarnianirudha8/byteaskai 2. Click Connect and complete OAuth in your MCP client (Claude, Cursor, VS Code, etc.) 3. MCP endpoint: https://byteaskai.run.tools
Tools (3)
-
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 val
-
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