MCP server for the Wisent Wire hardware testing platform — drive power, GPIO, UART/RS485/CAN, firmware flashing, and GDB debug from an AI agent
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"wisent-wire-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# wisent-wire-mcp MCP (Model Context Protocol) server for the [Wisent Wire](https://wisent-wire.com) hardware testing platform. Lets AI assistants interact with WisentWire devices — power control, firmware flashing & flasher catalog, UART / RS485 / CAN buses, GPIO control & telemetry, GDB debug sessions, device registry, reservations, and protocol frame definitions. ## Installation Requires Python **3.10+**. Install with [`pipx`](https://pipx.pypa.io) — it puts the MCP server in an isolated environment and adds the `wisent-wire-mcp` binary to your `PATH`. ### 1. Install `pipx` (one-time) ```bash # macOS brew install pipx pipx ensurepath # Linux / WSL python3 -m pip install --user pipx python3 -m pipx ensurepath ``` Open a new terminal so the updated `PATH` is picked up. ### 2. Install the MCP server ```bash pipx install wisent-wire-mcp ``` Verify: ```bash which wisent-wire-mcp # ~/.local/bin/wisent-wire-mcp (or similar) ``` ### 3. Upgrade / uninstall ```bash pipx upgrade wisent-wire-mcp pipx uninstall wisent-wire-mcp ``` ## Configuration ### `.mcp.json` location Claude Code reads MCP servers from `.mcp.json`. Two scopes: | Scope | Path | When to use | |-------|------|-------------| | **Project** | `<repo-root>/.mcp.json` | Shared with the project (checked into VCS or per-repo) | | **User** | `~/.claude.json` under the `mcpServers` key | Available in every Claude Code session for this user | Claude Desktop uses a separate file: | Platform | Path | |----------|------| | macOS | `~/Library/Application Support/Claude/claude_desktop_config.json` | | Windows | `%APPDATA%\Claude\claude_desktop_config.json` | | Linux | `~/.config/Claude/claude_desktop_config.json` | ### Example `.mcp.json` ```json { "mcpServers": { "wisent-wire": { "command": "wisent-wire-mcp", "env": { "WISENT_WIRE_API_KEY": "wwk_..." } } } } ``` After editing `.mcp.json`, restart Claude Code (or reload the window) for the server to be …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.