
Hyperiux Vault
io.github.Hyperiux-Immersion-LabsPublished by GitHub account Hyperiux-Immersion-Labsv0.3.0Updated Oct 24, 2026
Browse, inspect, and retrieve installable React and Next.js interaction effects from Hyperiux Vault.
Overview
Local MCP server that lets an assistant browse, search and inspect Hyperiux Vault's React/Next.js interaction effects and fetch installable source.
- What you can do
- Browse and search the effect catalog by name substring or category, with pagination and tier labels
- List all categories with effect counts to narrow a search
- Get full detail for one effect by exact slug: description, tier, dependencies, version, changelog and install command
- Retrieve an effect's full source when the account is entitled to it
- When to use it
- Useful when building React or Next.js interfaces and you want the assistant to find, compare and pull in ready-made interaction effects from the Hyperiux Vault registry instead of writing them from scratch.
- Requirements
- Runs locally over stdio via npx (Node.js). Listing, searching and metadata lookups need no account. Fetching source requires a signed-in Hyperiux account: a HYPERIUX_TOKEN environment variable or a saved hyperiux login session in ~/.hyperiux/auth.json. Pro effects need a Pro subscription.
Installation
In SourceWeft
- Open Hyperiux Vault in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
hyperiux-mcp-server
An MCP (Model Context Protocol) server for the Hyperiux Vault effect registry. Lets AI clients (Claude Code, Claude Desktop, Cursor, etc.) browse, search, and inspect React/Next.js interaction effects, and fetch installable source for effects they're entitled to.
Install
Add to your MCP client's config (e.g. claude_desktop_config.json or Claude Code's .mcp.json):
Signing in
Every effect's source needs a signed-in Hyperiux account - free effects too. This server reuses a token, checked in this order:
- the
HYPERIUX_TOKENenvironment variable (generate one at/cli-auth), then - a
hyperiux loginsession already saved by the Hyperiux CLI (~/.hyperiux/auth.json)
Without a token, hyperiux_get_effect with include_source: true returns the metadata (description, dependencies, changelog) and sign_in_required, telling you to run npx hyperiux login. Listing, searching and details lookups (include_source: false) need no token and never count as installs.
Fetching source counts against the account's daily install limit, shared with its website and CLI usage: 3 a day on Free, 5 on Pro, 10 on Pro+. Pro effects also need a Pro subscription; on a free account they return source_locked.
Tools
hyperiux_list_effects- browse/search the catalog by name substring and/or category, paginated. Each result includes its tier (free/pro).hyperiux_get_effect- full detail for one effect by exact slug: description, tier, dependencies, version, changelog, install command, and optionally full source.hyperiux_list_categories- every category with effect counts, for narrowing ahyperiux_list_effectssearch.
Development
Test against a running build with the MCP Inspector:
Known limitation
None of the tools return an effect's props yet - the registry has them, the tools just don't expose them today. hyperiux_list_effects reports each effect's tier but can't filter by it; count or filter the returned list yourself.
Source: packages/mcp-server/README.md at commit d184859
Tools
0Version history
2- v0.3.0LatestOct 19, 2026
- v0.2.1Sep 21, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts