HardwareMCP

io.github.saadvzPublished by GitHub account saadvzv0.1.0Updated Oct 30, 2026

Find MCP servers for ESP32, Arduino, 3D printers, Home Assistant, cameras and other hardware.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A hosted catalog server that helps an assistant find MCP servers for physical hardware such as ESP32, Arduino, Raspberry Pi, 3D printers and Home Assistant.

What you can do
  • Search the hardware MCP server catalog by query, device or category, with results sorted by GitHub stars
  • Read one server's full details: description, requirements, install commands and client config snippet
  • List every device family in the catalog with how many servers support it
  • Recommend the best servers for a specific device or model, optionally ranked by a goal such as flashing firmware or monitoring prints
When to use it
Useful when you are setting up an assistant to work with hardware and want it to point you to a suitable MCP server, its install commands and a ready client config, instead of searching the web yourself.
Requirements
A remote Streamable HTTP endpoint with no install, no API key and no authentication; some clients need a local bridge such as npx mcp-remote to connect to it.
Before you install
The catalog only recommends other servers; install commands and configs are copied from each project's README and have not been bench-tested, so review the code before giving an agent access to your hardware. The service is stateless and public, and queries are sent to a third-party endpoint.

Installation

In SourceWeft

  1. Open HardwareMCP 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.saadvz%2Fhardwaremcp/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": {
    "hardwaremcp": {
      "type": "http",
      "url": "https://hardwaremcp.khanex.ai/mcp"
    }
  }
}

README

hardwaremcp

[MCP Registry] [Remote endpoint] [Transport] [Auth] [Catalog] [License: MIT]

Remote endpoint: https://hardwaremcp.khanex.ai/mcp. Paste it into any MCP client: no install, no API key.

Ask your agent "which MCP server should I use for my Bambu P1S?" and it gets the right server, install commands and client config from the HardwareMCP catalog.

An MCP server that helps your AI agent find MCP servers for physical hardware: ESP32, Arduino, Raspberry Pi, RP2040, 3D printers (Bambu, Prusa, Klipper, OctoPrint), Home Assistant, cameras (Frigate, UniFi Protect, ONVIF), Zigbee, serial/BLE and lab gear.

It's a thin layer over the HardwareMCP catalog: 59 servers with install commands and client configs copied from their READMEs.

Tools

ToolWhat it does
search_servers(query, device?, category?)Search the catalog. Results sorted by GitHub stars.
get_server(slug)Full details: what it does, requirements, install commands, client config snippet.
list_devices()Every device family with server counts.
recommend_for_device(device, goal?)Top picks for a device or model (e.g. "Bambu P1S", "Voron", "ESP32-S3"), optionally ranked by a goal.

Use the hosted server (no install)

Endpoint: https://hardwaremcp.khanex.ai/mcp (Streamable HTTP, stateless, no auth, CORS open, JSON responses). POST handles JSON-RPC, OPTIONS returns 204 with CORS headers, and GET/DELETE return 405 because there are no sessions or server-initiated streams.

Claude Code

bash
claude mcp add --transport http hardwaremcp https://hardwaremcp.khanex.ai/mcp

Cursor (~/.cursor/mcp.json)

json
{ "mcpServers": { "hardwaremcp": { "url": "https://hardwaremcp.khanex.ai/mcp" } } }

Claude Desktop (claude_desktop_config.json)

json
{ "mcpServers": { "hardwaremcp": { "command": "npx", "args": ["-y", "mcp-remote", "https://hardwaremcp.khanex.ai/mcp"] } } }

Grok Bot (desktop app): there's no settings field for MCP URLs. In a Bot chat, send:

Add a custom MCP server named hardwaremcp at https://hardwaremcp.khanex.ai/mcp

Confirm when asked (no sign-in needed), then type @ and pick hardwaremcp. (Cursor forum answer)

Muse (Meta): ask Muse in chat to create a Custom Connector (Meta Help Center):

Create a Custom Connector for a new remote MCP server, then connect to it:- Name: hardwaremcp- Transport: remote streamable HTTP- URL: https://hardwaremcp.khanex.ai/mcp- Auth: none (public, no API key or OAuth)Then list its tools and call list_devices to confirm it works.

Run locally (stdio)

bash
npx -y hardwaremcp   # once published to npm
json
{ "mcpServers": { "hardwaremcp": { "command": "npx", "args": ["-y", "hardwaremcp"] } } }

Develop

bash
npm installnpm run gen-data      # regenerate src/data.ts from ../hardwaremcp/data/servers.jsonnpm run buildnpm test              # scripted client over stdionode test-client.mjs https://hardwaremcp.khanex.ai/mcp   # against the live endpoint

Caveat

Install commands come from each project's README and haven't been bench-tested by HardwareMCP. Review code before giving an agent access to your hardware.

License

MIT

Listed in

Source: README.md at commit ab832c4

Tools

4

search_servers

Search the HardwareMCP catalog of MCP servers for physical hardware (ESP32, Arduino, Raspberry Pi, 3D printers like Bambu/Prusa/Klipper/OctoPrint, Home Assistant, cameras, Zigbee, serial, oscilloscopes). Returns matching servers sorted by GitHub stars.

Parametersqueryrequireddevicecategory

get_server

Get full details for one server by slug: what it does, requirements, install commands, notes, and the MCP client config snippet copied from its README.

Parametersslugrequired

list_devices

List every device family in the catalog with how many MCP servers support it.

Takes no parameters.

recommend_for_device

Recommend the best MCP servers for a specific device, optionally for a goal (e.g. 'monitor prints', 'flash firmware', 'control lights'). Prefers maintained servers with ready client configs.

Parametersgoaldevicerequired

Version history

1
  1. v0.1.0LatestOct 16, 2026

Score

100% 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
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts