pi-controller-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | info |
| PI_CONTROLLER_URL | Yes | Pi-controller API URL | |
| PI_CONTROLLER_API_KEY | No | API key for authentication | |
| PI_CONTROLLER_TIMEOUT | No | Request timeout (ms) | 30000 |
| PI_CONTROLLER_PASSWORD | No | Password for authentication | |
| PI_CONTROLLER_USERNAME | No | Username for authentication | |
| PI_CONTROLLER_TLS_VERIFY | No | Verify TLS certs | true |
| PI_CONTROLLER_TLS_CA_CERT | No | Path to CA cert |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_clusterC | Create a new K3s cluster definition |
| list_clustersC | List all K3s clusters |
| get_cluster_statusA | Get detailed status of a cluster including nodes, workloads, and health |
| provision_clusterC | Provision a K3s cluster on Raspberry Pi nodes (async operation) |
| scale_clusterC | Scale a cluster by adding or removing worker nodes |
| delete_clusterA | Delete a cluster (must be deprovisioned first) |
| discover_nodesB | List all discovered Raspberry Pi nodes |
| get_node_infoB | Get detailed information about a specific node |
| register_nodeC | Manually register a Raspberry Pi node |
| provision_nodeB | Provision K3s on a single node |
| deprovision_nodeA | Remove K3s from a node and return to discovered state |
| list_gpio_devicesB | List all GPIO devices across all nodes |
| deploy_podC | Deploy a Kubernetes pod to a cluster |
| initialize_caC | Initialize the Certificate Authority for the cluster |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Cluster Status | Current cluster state, node count, and health metrics |
| Cluster Nodes | Detailed node information for cluster |
| Node Information | Hardware specs, OS info, and capabilities |
| Node Metrics | CPU, memory, temperature, and network metrics |
| GPIO Devices | List of GPIO devices on this node with current states |
| GPIO State | Current value and configuration of GPIO device |
| System Health | Overall pi-controller system health and API status |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dsyorkd/pi-controller-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server