The Model Hardware Standard explained.
A research preview of the Model Hardware Standard (MHS), sometimes shortened to MHS AI in early coverage, opened on August 27, 2026 — a shared, model-agnostic way for AI agents to operate programmable physical devices.
MHSBase turns the public project description into a clear, practical starting point for researchers, engineers, and curious builders.
Unofficial community resource — not affiliated with or endorsed by the Model Hardware Standard project or its contributors.
What is the Model Hardware Standard?
Model Hardware Standard is a shared specification for AI agents that need to work with physical equipment. It provides a common way to describe devices, expose their state, and issue operations instead of forcing every agent to learn a different vendor interface. People may refer to it as the MHS standard or an AI hardware standard, but the important idea is the shared device interface. The research preview is model-agnostic: the same MHS approach is intended to be usable with different models and agent harnesses. It is designed for any device with a programmable interface, from a microscope or liquid handler to a robotic arm on a lab or manufacturing floor.
Programmable devices
MHS is meant for devices with a programmable interface. The announcement names microscopes, liquid handlers, robotic arms, and other lab or manufacturing instruments as examples.
Model-agnostic access
MHS is not presented as a feature tied to one model. Different AI models and agent harnesses can use the same physical-device standard.
A standardized driver
A driver translates between a computer operating system and a hardware device, giving the agent a consistent interface across unlike equipment.
Agent-ready context
Device characteristics, capabilities, adjustable settings, and safety limits can be made available in a form an AI agent can understand and use.
How AI agents control physical devices with MHS
Once devices are connected and their capabilities are described, the announcement identifies three ways to control the hardware. Together they support interactive use, direct operation, and repeatable orchestration across multiple devices.
MCP
MHS can be accessed through the Model Context Protocol, giving an agent a standard protocol surface for interacting with and orchestrating physical devices.
CLI
A command-line interface provides a direct way to operate devices and inspect workflows without building a separate graphical control surface.
Code files
APIs and code files can chain driver commands for long-running tasks or operations that should run faster and more deterministically than online reasoning alone.
Questions worth answering early
MHS is a new research preview, so it helps to separate what the announcement says today from what the ecosystem may build next.
For access, current scope, and future releases, always check the official sources linked below.