Firmware Test Farm Mcp

io.github.oxyvore-cyberPublished by GitHub account oxyvore-cyberv0.1.0Updated Sep 29, 2026

Flash and run real firmware on physical embedded dev boards from an AI agent, over MCP.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Remote MCP server that lets an assistant flash compiled firmware onto real embedded dev boards and get structured pass/fail test results.

What you can do
  • Upload firmware binaries via short-lived signed URLs
  • Flash and run firmware on a chosen physical board type, returning pass/fail, serial log excerpt, crash and reset info, and timing
  • Check live queue status, boards available and estimated wait
  • Search a curated knowledge base of reference examples, known issues and pinout or datasheet links per board type
When to use it
Useful when an assistant needs to validate embedded firmware on real hardware rather than a simulator, for example checking that a build boots, runs, or fails in a specific way on boards such as Raspberry Pi Pico, Arduino Nano 33 BLE or ESP32 variants.
Requirements
A hosted remote endpoint over Streamable HTTP; no package to install. Requires an account and an API key created from the dashboard, sent as a bearer token in the Authorization header. Network access is needed.
Before you install
An account and API key are required, and the key is sent as a bearer token. Usage is metered: the free tier allows 50 firmware runs per month, with paid and Enterprise tiers beyond that, so runs can incur cost. Uploaded firmware is executed on shared physical hardware, so avoid sending proprietary binaries you do not want run on a third-party service.

Installation

In SourceWeft

  1. Open Firmware Test Farm Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.oxyvore-cyber%2Ffirmware-test-farm-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "firmware-test-farm": {
      "type": "http",
      "url": "https://test-farm-17d99.web.app/mcp"
    }
  }
}

README

firmware-test-farm-mcp

An MCP server that lets an AI agent flash a compiled firmware binary onto a real, physical embedded dev board, run it, and get back structured pass/fail results — serial output, crash info, reset reason, timing — instead of a simulator or a description of what should happen.

This repo hosts the server.json manifest for the MCP Registry. The server itself runs as a hosted, always-on remote endpoint — there's no package to install.

Connecting

Sign up and create an API key from the dashboard, then point any MCP client that supports Streamable HTTP + a bearer token at:

https://test-farm-17d99.web.app/mcp Authorization: Bearer

Tools

  • run_firmware_test — flashes the given firmware artifact onto a real board of the requested board_type and waits for a structured result (pass/fail, serial log excerpt, crash/reset info, timing). Every response includes live queue info (position, boards available, estimated wait) so an agent can decide whether to wait or come back later.
  • get_upload_url — returns a short-lived signed URL to upload a firmware binary to before calling run_firmware_test.
  • search_firmware_examples — searches a curated knowledge base of reference examples, known issues, and pinout/datasheet links for a given board type.

Currently available boards

heltec_wireless_tracker, arduino_giga_r1, xiao_nrf52840_plus, arduino_nicla_voice, arduino_nano_33_ble, adafruit_feather_esp32_v2, seeed_grove_vision_ai_v2, raspberrypi_pico

More board types are defined in the schema for future hardware; a submission for a board_type with no physical board currently registered is rejected up front rather than left queued forever.

Pricing

Every account starts on a free tier (50 firmware runs/month). Paid and Enterprise tiers are unlimited — Enterprise additionally covers custom board types and custom motors/controllers/sensors outside the standard fleet. See the dashboard for current usage and to request a tier change.

Source: README.md at commit 2a52bc3

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 17, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.