hyperdrive-mesh
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| p2p_drive_createB | Erstellt ein neues, kryptografisch gesichertes P2P-Hyperdrive und liefert den Public Key zum Teilen zurück. |
| p2p_drive_connectB | Verbindet sich mit einem bestehenden Remote-Hyperdrive über dessen 64-stelligen hexadezimalen Public Key via DHT. |
| p2p_file_writeB | Schreibt oder aktualisiert eine Datei im P2P-Hyperdrive. Die Änderung wird automatisch an verbundene Peers gestreamt. |
| p2p_file_readC | Liest eine Datei aus dem lokalen oder remote über P2P gestreamten Hyperdrive. |
| p2p_drive_listC | Listet alle Dateien und Verzeichnisse eines P2P-Hyperdrives auf. |
| p2p_swarm_statusB | Liefert den aktuellen Status aller gemounteten Drives und die Anzahl aktiver P2P-Peers im Hyperswarm. |
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 6 tools
Each tool targets a distinct resource plus action: swarm status, drive create/connect/list, and file read/write. There is no overlap — read vs write vs list are clearly separated, and drive vs file resources are unambiguous.
All six tools follow the exact same p2p_<resource>_<action> snake_case pattern (p2p_swarm_status, p2p_drive_create, p2p_file_write). Consistent verb placement and casing throughout.
Six tools is well-scoped for a P2P hyperdrive server, covering status, drive lifecycle, and file I/O without redundancy. Each tool clearly earns its place.
Core workflows (create, connect, list, read, write) are covered, but there is no delete operation for files or drives and no disconnect tool. These are notable lifecycle gaps an agent would hit when cleaning up or tearing down a drive.