Hyperfabric MCP Server

TypeScript MCP server for Hyperfabric API

Local serverstdioTypeScript

What is the Hyperfabric MCP MCP server?

Hyperfabric MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. TypeScript MCP server for Hyperfabric API.

What you get

An MCP (Model Context Protocol) server that enables LLMs to interact with Hyperfabric APIs. This server exposes all 79 Hyperfabric OpenAPI endpoints as tools for comprehensive infrastructure management and automation.

What the assistant can call

Once Hyperfabric MCP is connected, these are the calls the assistant has available:

  • authGetBearerTokens — List all bearer tokens for the user
  • authCreateBearerTokens — Create new bearer tokens
  • authGetBearerToken — Get specific bearer token details
  • authDeleteBearerToken — Delete a specific bearer token
  • authGetUsers — List all users in organization
  • authGetUser — Get specific user details
  • authSetUsers — Create or update users
  • authUpdateUser — Update existing user
  • authDeleteUser — Delete a user account
  • devicesGetDevices — List all devices (bound and unbound)
  • devicesBindDevice — Bind a device to a fabric node
  • devicesUnbindDevice — Unbind device from a fabric node

Setting it up

The server ships on npm as npm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need 3 environment variables: HYPERFABRIC_API_TOKEN, LOG_LEVEL, OPENAPI_SPEC_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js 18+ installed - VSCode with GitHub Copilot or Claude Desktop - Hyperfabric API credentials (API Token) - Hyperfabric OpenAPI specification file

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Hyperfabric MCP's toolset — authGetBearerTokens, authCreateBearerTokens, authGetBearerToken and 11 more — is a fair guide to whether it matches your workflow. It is maintained by jim-coyne; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Hyperfabric MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the hyperfabric mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
authGetBearerTokensList all bearer tokens for the user
authCreateBearerTokensCreate new bearer tokens
authGetBearerTokenGet specific bearer token details
authDeleteBearerTokenDelete a specific bearer token
authGetUsersList all users in organization
authGetUserGet specific user details
authSetUsersCreate or update users
authUpdateUserUpdate existing user
authDeleteUserDelete a user account
devicesGetDevicesList all devices (bound and unbound)
devicesBindDeviceBind a device to a fabric node
devicesUnbindDeviceUnbind device from a fabric node
fabricsGetAllFabricsList all fabrics in organization
fabricsAddFabricsCreate new fabrics

How to install the Hyperfabric MCP MCP server

{
  "mcpServers": {
    "hyperfabric": {
      "command": "npx",
      "args": ["-y", "npm"],
      "env": {
        "HYPERFABRIC_API_TOKEN": "your-value",
        "LOG_LEVEL": "your-value",
        "OPENAPI_SPEC_PATH": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js 18+ installed - VSCode with GitHub Copilot or Claude Desktop - Hyperfabric API credentials (API Token) - Hyperfabric OpenAPI specification file
VariableDescriptionRequired
HYPERFABRIC_API_TOKENCredential the server authenticates with.Yes
LOG_LEVELConfiguration value read at startup.Optional
OPENAPI_SPEC_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Hyperfabric MCP to authGetBearerTokens.
  • Use Hyperfabric MCP to authCreateBearerTokens.
  • Use Hyperfabric MCP to authGetBearerToken.

Frequently asked questions

It connects Hyperfabric MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (authGetBearerTokens, authCreateBearerTokens, authGetBearerToken, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Hyperfabric MCP directly.