RedPitayaCore-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RP_HOST | No | Required explicit unicast IPv4 address in live mode. Unset by default. | |
| RP_MODE | No | Server mode. Valid values are `mock` or `live`. Mock is the default and requires no hardware. | mock |
| RP_PORT | No | SDR TCP port. | 1001 |
| RP_TIMEOUT | No | I/O timeout from 0.1 through 10 seconds. | 3 |
| RP_ALLOW_RX | No | Operator permission for live RX state changes. | false |
| RP_SSH_PORT | No | SSH port. | 22 |
| RP_SSH_USER | No | Enables optional fixed read-only SSH diagnostics when set. Unset by default. | |
| RP_HTTP_PORT | No | HTTP metadata port. | 80 |
| RP_ALLOW_LIFECYCLE | No | Permission for mock lifecycle execution only. | false |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rp_profileA | Report configured capabilities and operator-reported target, without hardware I/O. |
| rp_device_diagnosticsA | Read bounded HTTP app metadata. Cannot verify running app/OS/FPGA identity. |
| rp_system_diagnosticsA | Read OS/model/process/app/FPGA evidence with optional fixed-command SSH; no writes. |
| rp_connection_probeB | TCP connect/close with no selector. Briefly occupies server accept; no identity proof. |
| rp_connection_statusB | Report local sockets/requested RX settings. No device setting or TX state readback. |
| rp_app_lifecycleC | Plan lifecycle URLs or simulate mock lifecycle. Live start/stop always blocked. |
| rp_rx_connectA | Open RX only, resetting RX config/FIFO. Live requires RP_ALLOW_RX and acknowledgement. Requires exclusive app ownership. Closing resets tuning/rate. No server ACK/readback. sample_rate: 20000, 50000, 100000, 250000, 500000 or 1250000 samples/second. |
| rp_rx_readB | Consume bounded buffered float32 IQ and return summary/preview; not calibrated RF. |
| rp_rx_disconnectA | Close owned RX sockets. Server resets RX tuning/rate; never opens TX sockets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| safety |
TDQS
Scored across 9 tools
Most tools are clearly separated by resource and action: diagnostics, connection checks, app lifecycle, and RX lifecycle are distinct. The diagnostics/status cluster (rp_profile, rp_device_diagnostics, rp_system_diagnostics, rp_connection_probe, rp_connection_status) has some conceptual overlap, but the descriptions clarify the boundaries and constraints.
All tools use a consistent rp_ prefix and snake_case, making the set predictable. The pattern is mostly rp_<domain>_<action>, though several diagnostic tools are noun-like rather than strict verb_noun, which is a minor deviation.
Nine tools is well-scoped for a hardware diagnostics and RX-control server. Each tool covers a distinct capability area without an excessive or thin surface.
The surface covers profile/diagnostics, connection checks, app lifecycle planning, and RX connect/read/disconnect. Minor gaps remain around live lifecycle operation and TX or deeper RX configuration/readback, but the core safe diagnostic and RX workflows are covered.