hardwaremcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_serversA | 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. |
| get_serverA | 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. |
| list_devicesA | List every device family in the catalog with how many MCP servers support it. |
| recommend_for_deviceA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct action: list_devices lists device families, search_servers searches by keyword, recommend_for_device recommends by device+goal, and get_server fetches details by slug. The only mild overlap is that both search_servers and recommend_for_device return server lists, but the descriptions clearly differentiate their inputs and purposes.
All tools use snake_case and follow a verb_noun pattern (list_devices, search_servers, get_server), with recommend_for_device being the only slight variation but still consistent with the same convention.
Four tools is well-scoped for a hardware MCP catalog: one for device families, one for recommendations, one for search, and one for details. Each tool has a clear, non-redundant role.
The surface covers discovery by device, goal-based recommendations, keyword search, and detailed server info. The only minor gap is a direct way to browse or list all servers without a query or device, but search_servers likely accommodates that.