Summary
The whole Hyperfabric API, one tool per endpoint.
Because the tools are generated from the OpenAPI specification rather than curated by hand, the parts most wrappers leave out — bearer tokens, user management — are reachable alongside the fabric operations.
What it is
A Node server that reads the Nexus Hyperfabric OpenAPI specification and generates one tool per endpoint, so the tool surface tracks the spec rather than a hand-written wrapper. That comes to 79 endpoints, and the names read like the API's own operations.
What you get
- Fabrics end to end: fabricsGetAllFabrics, fabricsGetFabric, fabricsAddFabrics, fabricsUpdateFabric, fabricsDeleteFabric
- The links between them: fabricsGetFabricConnections, fabricsGetFabricConnection, fabricsAddFabricConnections, fabricsSetFabricConnections, fabricsDeleteFabricConnections
- Devices: devicesGetDevices lists them, devicesBindDevice and devicesUnbindDevice attach and detach them
- Users and credentials: authGetUsers, authGetUser, authSetUsers, authUpdateUser, authDeleteUser, plus authGetBearerTokens, authGetBearerToken, authCreateBearerTokens and authDeleteBearerToken
- Because the tools are generated from the specification, the set moves with the API version you point it at
Requirements
Node.js 18 or newer, a Hyperfabric API token, and a copy of the Hyperfabric OpenAPI specification file for the server to read. Build with `npm install && npm run build`, then point the client at dist/main.js; the token and the log verbosity go in the same config block.