About Medius Docs
Medius Docs is a documentation site for the Medius input-passthrough firmware, its binary control protocol, and Rust library. It serves developers working with the device, with API references, language bindings, a browser dashboard, and AI-oriented access formats.
Key features
- 01Binary protocol and device behavior reference
- 02Rust library API documentation
- 03C ABI and Python bindings documentation
- 04Browser dashboard guidance
- 05Markdown pages and llms.txt
Use cases
- 01Look up Medius protocol commands
- 02Build against the medius Rust crate
- 03Consult C ABI or Python bindings
- 04Use the browser dashboard for device tasks
MCP support
The documentation site lists an MCP server in its AI Access section, but the provided README does not describe its capabilities.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://medius.k4tech.net/mcpclaude mcp add --transport http net-k4tech-docs https://medius.k4tech.net/mcp{"mcpServers":{"net-k4tech-docs":{"type":"http","url":"https://medius.k4tech.net/mcp"}}}Open in Cursor{"servers":{"net-k4tech-docs":{"type":"http","url":"https://medius.k4tech.net/mcp"}}}Open in VS Code{"mcpServers":{"net-k4tech-docs":{"type":"http","url":"https://medius.k4tech.net/mcp"}}}{"mcpServers":{"net-k4tech-docs":{"serverUrl":"https://medius.k4tech.net/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
5This tool takes no parameters.
Details
From the project READMEMedius Documentation
Documentation site for Medius: the input-passthrough firmware, its binary control protocol, and the medius Rust library.
Built with SolidJS and MidnightUI.
Sections
| Section | What |
|---|---|
| Native API | Binary control protocol and box behaviour: hardware, transport, frame format, injection model, every command (opcodes 0x01-0x1E). |
| Rust Library | medius crate reference: connecting, command bindings, keepalive, reconnect, and the async / mock / tracing features. |
| Bindings | C ABI and Python bindings over the crate. |
| Dashboard | In-browser box dashboard: connect, device info, firmware update, recovery, device log. |
| AI Access | Per-page Markdown twins, llms.txt, and the MCP server. |
Development
Prerequisites
Setup
bun install
Dev server
bun run dev
Open http://localhost:3000.
Build
bun run build
Output: dist/.
Tech stack
| Tool | Role |
|---|---|
| SolidJS | Reactive UI framework |
| @solidjs/router | Client-side routing |
| Vite | Build tool |
| Bun | Runtime and package manager |
| MidnightUI | Component library |
| solid-icons | Icons |
Deployment
CI builds the app and a multi-arch container on every push to main and publishes it to
ghcr.io/k4hvh/medius-docs. Run it:
docker run --rm -p 3000:3000 ghcr.io/k4hvh/medius-docs:latest
docker-compose.yml runs the same image. The container builds with Bun and serves dist/
on port 3000.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.