About Hyperiux Vault
Hyperiux Vault is an MCP server for AI clients to find and inspect React and Next.js interaction effects, and retrieve source for effects available to an account. Browsing and metadata lookups do not require sign-in; source retrieval uses Hyperiux account access.
Key features
- 01Browse and search effects by name or category
- 02View effect descriptions, dependencies, versions, and changelogs
- 03Retrieve install commands and eligible source
- 04List categories and effect counts
Use cases
- 01Find an interaction effect for a React or Next.js project
- 02Check an effect's dependencies and version before installation
- 03Retrieve source for an effect available to an account
MCP support
Exposes catalog browsing, search, category, and effect-detail tools to MCP clients. Source retrieval requires a signed-in Hyperiux account and is subject to account tier and daily install limits.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
3Saved tool list · updated 1w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | integer | No | Maximum results to return. |
| query | string | No | Case-insensitive substring match against effect name (e.g. 'cursor', 'text-reveal'). Omit to list all. |
| offset | integer | No | Number of results to skip for pagination. |
| category | string | No | Filter to one category, e.g. 'text', 'cursor', 'webgl', 'buttons', 'carousels', 'components', 'navigation', 'backgrounds', 'loaders', 'transitions'. Use hyperiux_list_categories to see all valid values with counts. |
Details
From the project READMEhyperiux-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):
{
"mcpServers": {
"hyperiux": {
"command": "npx",
"args": ["-y", "hyperiux-mcp-server"]
}
}
}
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
pnpm --filter hyperiux-mcp-server build # tsc -> dist/
pnpm --filter hyperiux-mcp-server test # vitest
pnpm --filter hyperiux-mcp-server lint # eslint
pnpm --filter hyperiux-mcp-server dev # tsx watch, for local iteration
Test against a running build with the MCP Inspector:
npx @modelcontextprotocol/inspector --cli node dist/index.js --method tools/list
npx @modelcontextprotocol/inspector --cli node dist/index.js --method tools/call --tool-name hyperiux_get_effect --tool-arg name=dotted-grid
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.