Hyperiux MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HYPERIUX_DEBUG | No | Set to 1 to enable verbose request logs — do not use in shared CI. | |
| HYPERIUX_TOKEN | No | Use a CLI token without saving it locally (useful in CI). | |
| HYPERIUX_API_URL | No | Override the API URL independently of the app URL. | |
| HYPERIUX_APP_URL | No | Override the Hyperiux app URL for self-hosting or testing. | |
| HYPERIUX_REGISTRY_URL | No | Override the registry URL for local development. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hyperiux_list_effectsA | Browse or search the Hyperiux Vault catalog of React/Next.js interaction effects (scroll systems, cursor trails, WebGL scenes, animated buttons, page transitions, etc). Each result includes tier ("free" or "pro") - use this to answer "how many free/pro effects are there" or "which of these are free" directly from one call, by filtering/counting the returned list yourself. Don't estimate or guess these counts, and don't call hyperiux_get_effect per-item just to total them up - it's unnecessary here. hyperiux_get_effect is still the right call for one specific effect's full description/props/changelog. Args:
Returns JSON: { total, count, offset, effects: [{ name, category, categories, dependencies, version, tier }], has_more, next_offset? } Examples:
|
| hyperiux_get_effectA | Get full details for one Hyperiux Vault effect by its exact slug - description, tier (free/pro), npm dependencies, version, changelog, and install instructions. Optionally includes full source code. Args:
Returns JSON: { name, title, description, tier, version, dependencies, changelog, install_command, preview_url, import_path, target, main, import_statement, files: [{ path, content? }] }
Pro effects without a token: the response still includes metadata (description, dependencies, changelog) but files have no content, and a note explains the effect requires a Hyperiux Pro account - don't treat this as an error, it's expected for unauthenticated Pro lookups. Free effects past the caller's daily install cap: the response still includes metadata but files have no content, and rate_limited/rate_limit_reason explain the daily limit and when to retry - also not an error, it's expected once the cap is hit. Examples:
Error Handling:
|
| hyperiux_list_categoriesA | List every effect category in the Hyperiux Vault catalog with how many effects are in each - useful before calling hyperiux_list_effects with a category filter, to confirm the exact category slug and see relative size. Returns JSON: { categories: [{ category, count }] }, sorted by count descending. Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool covers a distinct stage of the catalog workflow: listing categories, listing/searching effects, and fetching one effect's full details. There is no functional overlap between them, and the descriptions explicitly state when to use or avoid each tool.
All tool names follow the same `hyperiux_verb_noun` pattern: `hyperiux_list_categories`, `hyperiux_list_effects`, and `hyperiux_get_effect`. Verb usage is consistent and clearly maps to the action each tool performs.
Three tools is an appropriate, well-scoped count for a read-only catalog server. Each tool earns its place and together they cover browsing, searching, and retrieving detailed information without unnecessary surface area.
The tool set fully covers the natural catalog workflow: discover categories, browse or search effects, then retrieve full details and source for a specific effect. For this server's stated purpose, there are no obvious dead ends or missing operations.