ByteAsk Embedded MCP
Firmware references for an agent: registers, Modbus and SCPI with a quote and page number, and a refusal instead of a guess when data is missing
- 26 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The agent sends query text to the external ByteAsk server, and request_document requests are logged there
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/byteask-embedded-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The agent sends query text to the external ByteAsk server, and request_document requests are logged there
This is third-party code. Review the repository files before installing.
What it does
ByteAsk Embedded MCP is the open server behind the ByteAsk Embedded Docs service. It serves agents that write firmware, drivers and protocol code and have to take exact facts: register offsets, Modbus function codes, SunSpec points, SCPI commands, trip thresholds, API symbols. The server returns verbatim fragments with a section and page reference, not a composed answer. If no suitable source exists, the server replies "no confident match" and does not fill in a value. Three tools: search_docs searches the corpus and returns up to eight results, get_context expands a result to its whole section by result_id, and request_document asks for a missing document to be added, with the request logged server-side. The tool descriptions are tuned so an agent calls search when it sees a hex value, a Modbus code or an MCU part number. The hosted server is reached at https://mcp.byteask.ai/mcp. The repository holds the server itself, the stdio and Streamable HTTP transports, token checking and the search backend interface.
Who it is for. Embedded engineers whose agent writes drivers and protocol code and must not invent register values from memory.
Good fit when
- You need the Modbus function code that writes multiple registers, with the page number
- An agent writes an Ethernet controller driver and checks the ETH_DMACTXDLAR register name against the reference
- SunSpec point parameters for an inverter are checked against the document before going into code
- A SCPI command needs the exact wording from the instrument manual
- A document is missing from the corpus and a request to add it is filed through request_document
Not a fit when
- You need your own documents in the search: the corpus of licensed sources stays on ByteAsk's side
- You need synthesis or explanation: the server returns verbatim fragments, not a ready answer
- The work is outside embedded development: the corpus targets firmware and protocol references
- You need guaranteed protection for outside access: the token check in the repository is a stub
Example request
Which Modbus function code writes multiple holding registers? Answer with a quote from the reference and the page number.MCP
- Transport
- stdio, http
- Authentication
- not required
Environment variables
MCP_HTTP_AUTH_TOKENsecret- Token for an HTTP run; without it the server runs unauthenticated (development only).
BYTEASK_BACKEND- Backend module and factory in module:callable form; empty means the sample.
Limitations
The project is in beta. The repository holds only the server and a sample backend with a few illustrative records, while the search engine and the licensed corpus run on the hosted service's side. The HTTP token check is described as a stub with a shared secret, to be replaced with real authorization before public exposure. The last commit in the repository was made in June 2026. A local run needs Python 3.10 and uv.
How to disable. Run claude mcp remove byteask-embedded-docs. The server needs no local services, and after removal the agent stops calling mcp.byteask.ai.
FAQ
How do I connect ByteAsk Embedded Docs to Claude Code?
Run claude mcp add --transport http byteask-embedded-docs https://mcp.byteask.ai/mcp. For Codex and Cursor the README gives a variant through npx -y mcp-remote with the same address.
What does the server do when there is no answer?
It returns an honest "no confident match" and tells the agent not to invent a value. The server does not compose answers or substitute similar data.
Can I run the server locally with my own documents?
Yes, through the SearchBackend interface: implement the search and get_context methods and point to the module in the BYTEASK_BACKEND variable. Without it the sample with illustrative records starts.
Does the hosted server need a key?
The README does not mention a key for the hosted address: the connect command holds only the address. For your own HTTP run you can set a token through MCP_HTTP_AUTH_TOKEN.
What does request_document do?
It files a request to add a missing document to the corpus, and the request is logged on the server side.
Discussion
No questions or reviews yet.
Related
MCP serversRef's MCP server: documentation search for APIs and libraries that hands the agent only the relevant parts of pages
Docs MCP Server
Grounded Docs MCP Server
A local MCP server that indexes docs from websites, GitHub, npm, PyPI and files and gives the agent version-aware search
An MCP server that lets an agent read files, search code and run commands in a workspace
An MCP server for Codex with semantic search over 1C's Standard Subsystems Library documentation
A command-line debugger for MCP servers from Giant Swarm: a REPL for tools, OAuth 2.1 and an MCP server mode for Cursor
The MCP server turns OpenAPI operations into agent tools and sends real requests to the configured REST API.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| ByteAsk Embedded MCP (this card) | yes | not required | 26 | |
| Embedded Skills | no | 787 | skills for building, debugging and buses, not quote search in reference docs | |
| Context7 | yes | API key | 64,240 | injects library documentation of the right version, not register and protocol references |
README in short
The README explains the server's purpose, a quick start on uv, ways to connect to Claude Code, Codex and Cursor, and a tool table with an example response. It then covers the backend interface, environment variables, an HTTP run, the project layout and security measures.