Regennexus Mcp
io.github.ReGenNowPublished by GitHub account ReGenNowv0.1.1Updated Oct 25, 2026
AI-controlled hardware: GPIO, robotics, sensors, cameras, mesh networking for IoT
Overview
Local MCP server that lets an AI assistant control physical hardware — GPIO pins, sensors, cameras, robotic arms and mesh nodes — through RegenNexus UAP.
- What you can do
- Set and read GPIO pins and PWM duty cycles for motors, LEDs and servos, and read sensor values or scan the I2C bus. Send and read data over serial (UART) ports. Move a robotic arm to joint positions and open or close a gripper. Capture a single image from a camera. List connected devices and get device details such as CPU, memory, IP and temperature. Discover mesh nodes, ping them, send or broadcast messages, and find nodes by capability.
- When to use it
- Use it when you want an assistant to drive real hardware on or near the machine — toggling pins, reading sensors, moving a robot arm, taking a camera snapshot, or talking to mesh nodes over the LAN. It suits hobbyist, lab and prototyping setups rather than software-only work.
- Requirements
- Runs as a local Python process installed from PyPI (regennexus-mcp). Local mode needs the regennexus package on the same machine; remote mode needs a running UAP API server and the REGENNEXUS_ENDPOINT and REGENNEXUS_API_KEY settings. REGENNEXUS_MODE selects auto, local or remote; REGENNEXUS_CONFIG and REGENNEXUS_LOG_LEVEL are optional. Desktop only.
Installation
In SourceWeft
- Open Regennexus Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
RegenNexus MCP Server
[RegenNexus Logo]MCP (Model Context Protocol) server adapter for RegenNexus UAP - enabling AI-controlled hardware.
This package exposes RegenNexus hardware capabilities as MCP tools, allowing Claude Code, Claude Desktop, and other MCP-compatible AI clients to control physical devices.
Features
- Hardware Control: GPIO, PWM, robotic arms, sensors, cameras
- Mesh Networking: Discover and communicate with nodes over LAN (UDP/WebSocket)
- Serial/I2C: Communicate with microcontrollers and sensors
- Two Connection Modes: Local (direct import) or Remote (HTTP API)
- Auto-Discovery: Automatically detects installed RegenNexus and mesh nodes
- MCP Compatible: Works with Claude, Codex, Gemini, and any MCP client
Installation
Quick Start
1. Configure Claude Code
Add to your Claude Code MCP settings:
2. Use with Claude
Once configured, Claude can control hardware:
Configuration
Configure via environment variables:
Claude Code Config with Environment
Available Tools (Free Tier)
These tools are provided by the regennexus package (open source):
GPIO & Basic I/O
Sensors & I2C
Serial Communication
Robotics
Device Management
Camera
Mesh Network
Premium tools with additional capabilities are available separately.
Connection Modes
Local Mode (Recommended)
Requires regennexus package installed on the same machine. Directly imports UAP modules for minimal latency. No API server needed.
This is the recommended mode for most users.
Remote Mode (Advanced)
Connects to a UAP instance running as a service via HTTP API. Requires UAP API server to be running (regen server).
Auto Mode (Default)
Tries local first, falls back to remote if UAP not installed.
Running Standalone
Architecture
Development
Related Projects
- RegenNexus UAP - Universal Adapter Protocol
- MCP Specification - Model Context Protocol
License
MIT License
Source: README.md at commit 510e35d
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts