Balena MCP
Related Servers
Alternatives to Balena MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA standalone MCP server that exposes Rancher-side tools, forwards Authorization headers or uses configured credentials, and supports HTTP and stdio transports.MIT
- FlicenseNot gradedqualityCmaintenanceEnables creation of MCP servers with both stdio and HTTP transports, providing CRUD tools, resources, and prompts for user management, along with a CLI client for testing and integration.-

thalovant-mcpofficial
AlicenseNot gradedqualityAmaintenanceMCP server for Thalovant control-plane and hub runtime APIs, supporting local stdio and remote Streamable HTTP with authentication and per-principal credentials.298 npmMIT
zynohostingofficial
FlicenseNot gradedqualityBmaintenanceEnables management of ZynoHosting sites, files, and deployments through a local stdio MCP server.61 npm-- AlicenseNot gradedqualityAmaintenanceMCP server and CLI for host and container operations, enabling Docker and Compose control, SSH, host inspection, logs, ZFS, and safe file transfer. It exposes flux and scout MCP tools with parity from the original TypeScript server.2AGPL 3.0
- FlicenseAqualityBmaintenanceExposes the official lark-cli as an MCP server, enabling agents to execute arbitrary CLI commands, query API schemas, and manage authentication.41-
TDQS
Scored across 41 tools
Most tools are clearly scoped to a single resource and action, such as list_fleets, create_tag, or pin_device_release, so an agent can usually tell them apart. The main ambiguity is balena_query_resource, which overlaps with every specific list/get tool, and the release-pinning tools also require careful reading.
All tools share a consistent balena_ prefix and mostly follow a verb_noun snake_case pattern, which makes the set predictable. Minor inconsistencies between add and create, or update and set, are present but do not seriously harm usability.
At 41 tools, the surface is well beyond the typical well-scoped range and will present agents with a long selection list. The generic query_resource tool also makes many of the specialized list/get tools feel like optional convenience wrappers rather than essential additions.
The set covers the main Balena workflows well: organizations, teams, fleets, devices, releases, tags, and variables, with solid CRUD-style coverage for tags and variables. Notable gaps such as organization creation, release deletion, and remote device actions are noticeable but not fatal to the core management workflow.