The chip vendors showed up: hardware MCP servers, six months later

I audited every hardware MCP server I could find, and the method had a hole in it big enough to drive a foundry through.

I started from the community awesome list, then the official MCP Registry, then targeted searches. All three index community projects. None of them index what a silicon vendor puts behind a login on its own developer portal. The registry is still labeled "in preview", and returns two firmware-adjacent results for "firmware" and nothing at all for "microcontroller".¹ The community list contains no first-party vendor servers.² So the audit reported a category of hobby projects, which was true of the layer I could see and wrong about the layer I could not.

Between October 2025 and August 2026, seven silicon and tooling vendors shipped first-party MCP servers or MCP-driven tooling: Arm, Nordic, Analog Devices, Espressif, Microchip, Silicon Labs and Texas Instruments. That is the industry deciding, quietly and without a joint announcement, that agent-callable endpoints are part of a developer offering now.

Every hardware MCP server I could find still holds up as a picture of the community layer. This is the layer above it, plus two corrections I owe the category.

The vendors that shipped

Checked 2026-08-13. Where a server is closed and hosted, all I can report is what the vendor documents.

Vendor	What shipped	When	License	What the agent gets
Arm	Arm MCP Server3	GA Oct 2025	Apache-2.0	x86→Arm migration scanning, sysreport, container image architecture checks, doc search, and apx_recipe_run profiling against a remote Arm target over SSH
Arm	Performix Dynamic Insights, MCP server built in (apx mcp start)4	Aug 2026	Proprietary, free download	generate_ai_insights, read_ai_insights_payload_details, list_recipes, list_runs. Needs a completed profiling run on a real Arm target
Nordic	MCP server for nRF Connect SDK5	May 2026	Proprietary, myNordic account	Slash commands for install, build, program, debug, UART and board tasks; the MCP tools are semantic search over SDK docs, DevAcademy and DevZone
Nordic	nRF Cloud MCP server6	May 2026	Proprietary, OAuth	16 read-only tools over your fleet: device metadata, timeseries and vitals, issues and traces with optional log excerpts, version stats, project listing
Analog Devices	CodeFusion Studio AI Debug Assistant7	Mar 2026 (preview)	Apache-2.0 repo	23 tools, 10 diagnostic prompts: session control, live register/memory/variable/stack/thread inspection, breakpoints, guarded GDB, Cortex-M and RISC-V fault decoding, ELF analysis. Needs a live debug session on real ADI silicon
Espressif	ESP-IDF Tools Local MCP Server8	Apr 2026	Apache-2.0	set_target, build_project, flash_project, clean_project, plus project://config, project://status and project://devices. Needs ESP-IDF v6.0+ and a board to flash
Espressif	Documentation MCP Server9	Apr 2026	Proprietary, free, login	One tool: search_espressif_sources(query, language)
Microchip	MCP Server + MPLAB-DOCS MCP Server10	Nov 2025	Proprietary, free, no auth	SearchProducts, SearchProductPhysicalSpecs, SearchProductInventoryInfo, SearchProductComplianceInfo, SearchMicrochipProductDocuments; semantic search over docs, examples, reference designs
Silicon Labs	MCP Server11	≈ Jan 2026	Proprietary	Docs and SDK search from Cursor, VS Code or Claude Code
Silicon Labs	Simplicity Network Analyzer MCP12	Jun 2026 (v1.0.0)	Proprietary, in Simplicity Studio 6	The agent discovers and executes the packet sniffer's own API operations. Needs a physical radio capture setup
Texas Instruments	Code Composer Studio bundled servers: ccs-debug, ccs-project, ccs-sysconfig, ccs-serial13	CCS 21.0.0, experimental in 20.2.0	Proprietary, local only	Build, project, SysConfig, serial and debug control. Needs CCS open and, for debug, an XDS110-class probe on real TI silicon
Golioth	tinymcp14	Jul 2025	Apache-2.0	Exposes on-device RPCs registered through the Golioth Firmware SDK as MCP tools, via Golioth's cloud. Needs a device already provisioned on Golioth

Golioth is in the table as a first-party device-cloud provider, but it is not one of the seven silicon and tooling vendors counted in the opening.

Arm's server sits at 90 GitHub stars as of August 2026, which for a first-party release is neither impressive nor embarrassing. Golioth's tinymcp has 152 and has taken no push since it launched in July 2025. Everything else from a vendor here is closed-source with no public activity signal, which tells us nothing about private usage.

This is the concrete form of an argument I made in the abstract in hardware is becoming an API.

Sort them by what the agent is actually handed

"Shipped an MCP server" treats a documentation search box and a live debug session as the same event. Sort those twelve entries by what an agent gets back from a tool call and the distribution goes lopsided fast.

Category	First-party entries	Which ones
Documentation and catalog lookup	3	Espressif Documentation, Microchip, Silicon Labs MCP — retrieval and nothing else
Toolchain control: build, flash, configure	3	Espressif ESP-IDF Tools, Nordic nRF Connect SDK, TI project and SysConfig
Live debug or capture on attached hardware	4	ADI CodeFusion, TI ccs-debug, Silicon Labs Network Analyzer, Arm Performix
Fleet data from devices you already deployed	2	nRF Cloud, Golioth tinymcp
Simulated execution	0	—

Three of twelve stop at retrieval — a quarter of the first-party category whose entire function is answering a question about a datasheet. Useful, honestly labeled, and the easiest thing on this list to build: a vector index over documents the vendor already owns, with one search tool on top.

The ordering surprised me. Arm was first, in October 2025, then Microchip in November and Silicon Labs around January 2026 — the last two with documentation search and nothing else. The MCU vendors whose developer tooling people actually argue about did not lead. Those two got to market six months early by shipping the tier that needs no hardware, no session state and no support burden.

The zero row matters more than the rest. Several servers can build or configure firmware without a board. None lets an agent execute the resulting binary without attached hardware. Live debug, capture, flashing and fleet observation still terminate at a physical object: a board, a probe, a capture rig or a deployed device. The vendors shipped agent access to the tools around the hardware. They did not ship a hardware-free target.

Three vendors have shipped nothing, and one took a different route

"Chip vendors have shipped MCP servers" is half true, and the other half is specific.

I found no official MCP server from STMicroelectronics. Every STM32-targeting server I found — shieldyguy/stm32-mcp, creativec09/stm32, stm32-gdb-mcp — is an independent project wrapping ST's public toolchains, none published or endorsed by ST. That is the largest gap on the board, because STM32 is what most of those community projects aim at.

I found no MCP integration in Infineon's ModusToolbox material. I also found no official server from Renesas — the only hit is a third-party VS Code extension by an unaffiliated publisher wrapping e2 studio.

NXP took a different route. An NXP engineer demoed a Zephyr-based MCP server for MCX MCUs on the company's own developer-relations channel in late March 2026. The code merged into upstream Zephyr on June 11 as a library, samples and unit tests.¹⁵ It ships as an open-source RTOS component, not a first-party NXP product with its own endpoint or support commitment. That is why it is not in the vendor-product table above.

Then the absence I find hardest to explain. I found no maintained MCP integration for Antmicro's Renode. Renode is deterministic, scriptable, CI-first, and models whole boards including peripherals — one of the most agent-shaped tools in existence, and the wrapper is close to trivial. Its official integrations use other interfaces, including WebSockets, rather than MCP.

The community layer is still where the strange things live

Serial and UART wrappers remain the most-reimplemented thing in the category: qarnet/serial-mcp in Rust, alxgmpr/serial-mcp in Python, es617/serial-mcp-server, all MIT and all in the single-digit-to-teens star range as of August 2026. Probe wrappers are the next layer up — es617/dbgprobe-mcp-server for J-Link, CMSIS-DAP and ST-Link, microhenrio/openocd-mcp, and okhsunrog/flashprobe-mcp doing probe-rs and espflash with RTT and defmt capture.

For simulation there is exactly one official option, labeled experimental by its own authors: Wokwi's CLI has an MCP mode, documented on a single page and gated on a token.¹⁶

The oddest entry is quantumnic/mcpd, an MCP server that runs on the ESP32 or RP2040 rather than on the host, exposing 106 built-in tools from the device itself.¹⁷ I do not know yet whether that inversion is a good idea.

Two corrections, because "agentic" is not "MCP"

Two projects are routinely described as hardware MCP servers and neither is one. Both are good projects; the mistake is vocabulary, not credibility.

EmbedAgents stm32-substrate is five Claude Code slash commands wrapping a Python CLI that shells out to ST's CubeProgrammer, CubeIDE, CubeMX, gdbserver and Signing Tool. Its .claude-plugin/plugin.json registers only "commands" — no mcpServers key, no MCP SDK import, no mention of MCP in the README, CHANGELOG or manifest.¹⁸

ccattuto/esp-agentic-dev is a CLI and shell-exec framework — esp_target.py, rtt_reader.py, svd_parser.py — invoked by Claude Code as subprocesses, talking to hardware over OpenOCD's Tcl port. No MCP SDK, no mcpServers configuration, no mention of MCP anywhere in the repository.¹⁹

Both do real work. Neither speaks the protocol. "Agentic" and "MCP" have become interchangeable in casual writing and they are two different claims: one is about what a tool is for, the other about a wire format and a discovery mechanism. If you are counting a category, that distinction is the measurement.

Three test-automation vendors I checked market agentic workflows heavily and have no MCP server anywhere in their material; "AI-powered" on a landing page is not evidence an endpoint exists.

Embedder thinks the whole approach is wrong

One company has looked at MCP servers for hardware and declined on purpose. Embedder ships an MCP client, not a server, and has publicly argued that its harness has agents write and execute code directly rather than going through tool-call round-trips.²⁰²¹

That deserves a hearing rather than a dismissal. A fixed tool schema is a lossy interface to a general-purpose machine: every capability you did not anticipate becomes a feature request, and every interaction costs a round trip through the model.

The counter-argument is boring and mostly about blast radius. A schema is a contract you can audit, rate-limit and refuse; "write and execute code directly" against a probe on somebody's bench is a different risk conversation. Both models will be around. This is not settled.

The missing capability is a hardware-free target

An agent working on firmware can, today, look up a register in a reference manual, build the project, flash a board, halt a core, decode a fault and read telemetry off a fleet. Building can happen without a board; execution, live debug and observation still need hardware attached somewhere. What the first-party category cannot do is close that loop without the physical object: take an ELF it just produced and find out whether it runs. E2B gave agents a computer they did not physically own, which is why a coding agent can iterate at three in the morning without a human. The firmware equivalent is the empty row in that capability table, and the same empty slot I mapped in the agent infrastructure map.

The vendors shipped manuals and controls. What an agent needs is a target.

Disclosure, since it is why I keep counting this category: we build one. Chiplab is a hosted MCP server that runs firmware on virtual instances of real Cortex-M parts, which is why it is in none of the tables above.

The only reliable way to find out whether your vendor has an agent endpoint is to read that vendor's developer site, which is a poor state of affairs for a protocol whose whole pitch is discoverability.

Sources

Footnotes

1. "The MCP Registry." Model Context Protocol. https://registry.modelcontextprotocol.io ↩

2. beriberikix. "Awesome MCP for Hardware." GitHub. https://github.com/beriberikix/awesome-mcp-hardware ↩

3. Arm. "Arm MCP Server." GitHub. https://github.com/arm/mcp ↩

4. Arm. "Arm Performix Dynamic Insights: agentic development." Arm Newsroom, August 3, 2026. https://newsroom.arm.com/blog/arm-performix-dynamic-insights-agentic-development ↩

5. Nordic Semiconductor. "AI-assisted development." nordicsemi.com. https://www.nordicsemi.com/Products/Technologies/AI-assisted-development ↩

6. Nordic Semiconductor. "MCP server." nRF Cloud documentation. https://docs.nrfcloud.com/docs/platform/mcp-server ↩

7. Analog Devices. "CodeFusion Studio." GitHub. https://github.com/analogdevicesinc/codefusion-studio ↩

8. Espressif. "ESP-IDF Tools Local MCP Server." Espressif Developer Portal, April 2026. https://developer.espressif.com/blog/2026/04/esp-idf-tools-mcp-server/ ↩

9. Espressif. "Documentation MCP Server." https://mcp.espressif.com/docs ↩

10. Microchip Technology. "Model Context Protocol Server." microchip.com. https://www.microchip.com/en-us/resources/model-context-protocol-server ↩

11. Silicon Labs. "Silicon Labs MCP Server." https://mcp.silabs.com ↩

12. Silicon Labs. "Simplicity Network Analyzer release notes." Silicon Labs documentation. https://docs.silabs.com/network-analyzer/latest/network-analyzer-release-notes/ ↩

13. Texas Instruments. "AI features in Code Composer Studio," CCS 21.0.0 User's Guide. https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs_21.0.0/ccs_ai.html ↩

14. Golioth. "tinymcp." GitHub. https://github.com/golioth/tinymcp ↩

15. Zephyr Project. "Zephyr MCP Server," pull request 105299, merged June 11, 2026. https://github.com/zephyrproject-rtos/zephyr/pull/105299 ↩

16. Wokwi. "MCP Support." Wokwi Docs. https://docs.wokwi.com/wokwi-ci/mcp-support ↩

17. quantumnic. "mcpd." GitHub. https://github.com/quantumnic/mcpd ↩

18. EmbedAgents. "stm32-substrate." GitHub. https://github.com/EmbedAgents/stm32-substrate ↩

19. ccattuto. "esp-agentic-dev." GitHub. https://github.com/ccattuto/esp-agentic-dev ↩

20. Embedder. "MCP servers." Embedder documentation. https://docs.embedder.com/integrations/mcp-servers ↩

21. Jonah Perry. "I'm going to have to hate a bit on MCP servers for agentic context and execution." LinkedIn, August 5, 2026. https://www.linkedin.com/posts/jonah-perry-941481161_im-going-to-have-to-hate-a-bit-on-mcp-servers-activity-7490879455523987458-V37q ↩