# pymcuprog-mcp

Source: https://glimind.com/server/pypi%2Fpymcuprog-mcp
Registry id: `pypi/pymcuprog-mcp`
Status: unknown

## Install

```json
{
  "mcpServers": {
    "pymcuprog-mcp": {
      "command": "uvx",
      "args": [
        "pymcuprog-mcp"
      ]
    }
  }
}
```

Claude Code:

```sh
claude mcp add pymcuprog-mcp -- uvx pymcuprog-mcp
```

## Tools (17)

- `build_and_flash`: Run make in a project directory, then flash the resulting .hex
- `disconnect`: Close the persistent debugger session
- `erase`: Chip erase or erase a specific memory area
- `flash`: Erase + write + verify + release in one call (recommended)
- `hold_in_reset`: Hold target in reset
- `list_connected_tools`: USB HID debuggers currently attached
- `list_supported_devices`: All device names pymcuprog knows (no hardware needed)
- `ping`: Read device ID bytes to verify connectivity
- `read_memory`: Read raw bytes from flash, EEPROM, fuses, etc.
- `read_supply_voltage`: Read debugger supply setpoint
- `read_target_voltage`: Measure target VCC
- `read_tool_info`: Read debugger firmware/hardware info
- `release_from_reset`: Release target from reset
- `set_supply_voltage`: Set debugger supply voltage output
- `verify_hex`: Compare target memory to a .hex file
- `write_hex`: Program a .hex file with manual control over erase/verify steps
- `write_memory`: Write raw hex bytes to fuses, EEPROM, user_row, etc.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
