mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --host | No | Explicit bind address; wins over --local. | |
| --http | No | Serves Streamable HTTP at POST /mcp instead of stdio, on all interfaces (0.0.0.0). HTTP mode is key-gated and requires mcp.api_key from every caller. | |
| --port | No | HTTP listen port. | 8315 |
| --local | No | Binds the HTTP listener to loopback (127.0.0.1) only. | |
| --config | No | Keep both config files in this folder instead of ~/.ctrlpi/. | |
| --no-scan | No | Never sweep the LAN, at startup or after. A first run with no config still sweeps once. | |
| --rotate-keys | No | Replace the shipped default key on any agent still using it with a random one, and record the date under key_set. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_agents_listA | List configured agents (Pi, Pico or ESP32). Returns name, ip, port, online (live /hello probe), type (pi/pico/esp32), version, has_default_key, and last_updated_at (UTC "YYYY-MM-DD HH:MM:SS", when the agent list was last saved; every sweep saves it). Unreachable agents are included (online=false). The LAN is swept automatically every hour. Pass rescan=true to sweep it now, but only when the user asks to find new hardware: a sweep takes 10 seconds or more. If has_default_key is true for any agent, tell the user that agent is on the insecure default key and ask whether to change it. |
| mcp_gpio_readB | Read a GPIO pin value on |
| mcp_gpio_writeA | Write a value to a GPIO pin on |
| mcp_gpio_scanA | Scan all hardware GPIO pins on |
| mcp_gpio_configA | Configure a GPIO pin on |
| mcp_gpio_watchedB | List the GPIO pins that are currently being actively watched (the ones emitting hardware interrupts/webhooks). |
| mcp_sensor_configA | Configure a named sensor on |
| mcp_sensor_readA | Read sensors on |
| mcp_script_listA | List the files in |
| mcp_script_readA | Read one file from |
| mcp_script_writeA | Create or overwrite a file in |
| mcp_script_runA | Run a file from |
| mcp_config_readB | Read |
| mcp_config_writeA | Update |
| mcp_config_loadA | Load a full config onto |
| mcp_agent_restartA | Restart |
| mcp_agent_upgradeA | Upgrade |
| mcp_agent_logsA | Read the last 50 lines of |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Most tools map cleanly to a resource+action (script, gpio, sensor, config, agent), but there are a few soft overlaps: mcp_gpio_scan versus mcp_gpio_read with 'all', and mcp_config_write versus mcp_config_load both mutate configuration. Descriptions do distinguish them (scan includes pin metadata/type/pull/reversed, load replaces whole config with a backup), so an agent can resolve the boundary, but the pairs are close enough to occasionally misselect.
Every tool follows the same mcp_<resource>_<verb> snake_case pattern: script_list/read/write/run, gpio_scan/read/write/config/watched, sensor_config/read, config_read/write/load, agent_restart/upgrade/logs. No camelCase or verb-style deviations anywhere.
18 tools is on the upper end but the server genuinely spans several sub-domains (scripts, GPIO, sensors, global config, agent lifecycle), and each tool covers a distinct operation. It's slightly heavy but no tool looks superfluous.
Coverage is strong: scripts have list/read/write/delete/run, GPIO has scan/read/write/config/watched with removal via config, sensors have config/read with delete, config has read/write/load/reset, and agent has list/restart/upgrade/logs. The notable gap is agent management — there is no tool to add or remove an agent entry, even though the server manages an agents-config.json.