pb-hypernode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HYPERNODE_API_TOKENS | Yes | JSON object mapping Hypernode app names to their API tokens, e.g. '{"myapp":"token1","myapp2":"token2"}'. Keys are the allowlist of apps the plugin can operate on. Required to authenticate with the Hypernode API. | |
| HYPERNODE_KNOWN_ADMIN_PATHS | No | Optional JSON object mapping Hypernode app names to their admin paths, e.g. '{"myapp":"/admin-custom"}'. If set for an app, brancher_create skips runtime admin-path discovery. If omitted, the plugin attempts discovery (with fallback to /admin). |
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 |
|---|---|
| brancher_ssh_infoC | Return SSH connection details (host, user, port) for a Brancher node. |
| brancher_listB | List active Brancher nodes for |
| brancher_deleteA | Delete a Brancher node, gated behind a |
| brancher_execA | Execute |
| brancher_putB | Sync |
| brancher_createC | Create a Brancher node, wait for it, sanitize it, and report it ready. |
| brancher_appsA | List every Hypernode |
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 7 tools
Each tool serves a unique purpose: ssh_info retrieves connection details, list enumerates nodes, delete removes a node, exec runs commands, put syncs files, create provisions a node, and apps lists configured apps. There is no functional overlap or ambiguity.
All tools share the 'brancher_' prefix, but the naming pattern is inconsistent: most use verb-noun (list, delete, exec, put, create) while two are noun-only (ssh_info, apps). This creates minor inconsistency in verb usage and clarity.
Seven tools is a reasonable number for managing Brancher nodes—covering core CRUD operations plus execution, file sync, and SSH info. It is neither sparse nor overwhelming for the domain.
The tool surface covers the full lifecycle of a node: create, list, delete, execute commands, sync files, retrieve SSH details, and list apps. No essential operation appears missing for the stated purpose of managing Brancher nodes.