authGetBearerTokensLABSCO 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.
Setup effort
Build from source
USE CASES
01
Taking stock of the fabrics you run
List them all, then open the one you were asked about.
02
Standing up a new fabric and wiring it in
Create the fabric, then add and set the connections that join it to what you already have.
03
Moving a device between fabrics
Find it, unbind it from where it is, bind it where it belongs.
04
Auditing who has API access
Users and the bearer tokens issued to them, read in the same session.
05
Rotating a bearer token
Issue the replacement first, then delete the old one.
06
Retiring a fabric cleanly
Read its connections, remove them, then delete the fabric — in that order.
79 tools
Listed in project docs. Your client may show a different list.
authCreateBearerTokensauthGetBearerTokenauthDeleteBearerTokenauthGetUsersauthGetUserauthSetUsersauthUpdateUserauthDeleteUserdevicesGetDevicesdevicesBindDevicedevicesUnbindDevicefabricsGetAllFabricsfabricsAddFabricsfabricsGetFabricfabricsUpdateFabricfabricsDeleteFabricfabricsGetFabricConnectionsfabricsAddFabricConnectionsfabricsGetFabricConnectionfabricsSetFabricConnectionsfabricsDeleteFabricConnectionsfabricsDeleteFabricConnectionfabricsGetFabricCandidatesfabricsGetFabricCandidatefabricsCommitFabricCandidatefabricsRevertFabricCandidatefabricsReviewFabricCandidatenetworksGetFabricStpnetworksUpdateFabricStpnetworksResetFabricStpnodesGetFabricNodesnodesAddFabricNodesnodesGetNamedFabricNodenodesUpdateFabricNodenodesDeleteFabricNodenodesGetPortsnodesGetPortnodesUpdatePortnodesSetPortsnodesResetPortnodesGetManagementPortsnodesAddManagementPortsnodesGetManagementPortnodesUpdateManagementPortnodesGetNodeLoopbacksnodesAddNodeLoopbacksnodesGetNodeLoopbacknodesUpdateNodeLoopbacknodesDeleteNodeLoopbacknodesGetNodeSubInterfacesnodesAddNodeSubInterfacesnodesGetNodeSubInterfacenodesUpdateNodeSubInterfacenodesDeleteNodeSubInterfaceportchannelsGetAllPortChannelsportchannelsAddPortChannelsportchannelsGetPortChannelportchannelsUpdatePortChannelportchannelsDeletePortChannelvnisGetFabricVnisvnisAddFabricVnisvnisGetFabricVnivnisUpdateFabricVnivnisDeleteFabricVnivnisGetFabricVniMembersvnisAddFabricVniMembersvnisGetFabricVniMembervnisDeleteFabricVniMembervrfsGetFabricVrfsvrfsAddFabricVrfsvrfsGetFabricVrfvrfsUpdateFabricVrfvrfsDeleteFabricVrfvrfsGetFabricStaticRoutesvrfsAddFabricStaticRoutesvrfsGetFabricStaticRoutevrfsUpdateFabricStaticRoutevrfsDeleteFabricStaticRouteBEFORE YOU INSTALL
What to know first
Tools you get
79 tools named in the project's documentation.
Requires
- Node.js 18+
- HYPERFABRIC_API_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/jim-coyne/hyperfabric_MCP
cd hyperfabric_MCP
npm install
npm run buildMCP Clients
VS Code
VS CODE · JSON
{
"servers": {
"hyperfabric": {
"command": "node",
"args": [
"<YOUR_PATH_TO_HYPERFABRIC_MCP_SERVER>/dist/main.js"
],
"env": {
"HYPERFABRIC_API_TOKEN": "<YOUR_HYPERFABRIC_API_TOKEN>",
"LOG_LEVEL": "info"
}
}
}
}Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"hyperfabric": {
"command": "node",
"args": [
"<YOUR_PATH_TO_HYPERFABRIC_MCP_SERVER>/dist/main.js"
],
"env": {
"HYPERFABRIC_API_TOKEN": "<YOUR_HYPERFABRIC_API_TOKEN>",
"LOG_LEVEL": "info"
}
}
}
}
