Skip to main content
Glama
Hyperiux-Immersion-Labs

Hyperiux MCP Server

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HYPERIUX_DEBUGNoSet to 1 to enable verbose request logs — do not use in shared CI.
HYPERIUX_TOKENNoUse a CLI token without saving it locally (useful in CI).
HYPERIUX_API_URLNoOverride the API URL independently of the app URL.
HYPERIUX_APP_URLNoOverride the Hyperiux app URL for self-hosting or testing.
HYPERIUX_REGISTRY_URLNoOverride 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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:

  • query (string, optional): substring match against effect name

  • category (string, optional): filter to one category slug

  • limit (number, default 30, max 100)

  • offset (number, default 0)

Returns JSON: { total, count, offset, effects: [{ name, category, categories, dependencies, version, tier }], has_more, next_offset? }

Examples:

  • "What cursor effects are available?" -> category="cursor"

  • "Is there anything with 'particles' in the name?" -> query="particles"

  • "How many free effects are there?" -> call with a limit high enough to cover total (check total/has_more first), then count tier === "free" yourself.

  • Don't use when: you need one effect's full description/props/changelog - use hyperiux_get_effect instead.

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:

  • name (string): exact effect slug

  • include_source (boolean, default false): also return component source. Needs a signed-in account for every effect (see below) and counts as one of the day's installs; details-only lookups (false) don't.

Returns JSON: { name, title, description, tier, version, dependencies, changelog, install_command, preview_url, import_path, target, main, import_statement, files: [{ path, content? }] }

  • changelog: array of { version, date, summary, breaking }, newest first

  • files[].content is omitted unless include_source=true AND the caller is signed in (and on Pro, for a Pro effect)

  • import_statement is the exact import line to use after installing (e.g. import DottedGrid from "@/components/effects/dotted-grid";), built from exportKind/exportName/import_path the same way the CLI's own hyperiux add output does - omitted if the registry entry has no import_path

  • install_limit/install_remaining: present on a normal (non-rate-limited) lookup, telling you how many more distinct effects this identity can fetch today - mention this to the user when remaining is low, same as the website's copy toast and the CLI's own "N of M daily installs left" line

No token (or an invalid one) with include_source=true: the response still includes metadata, but files have no content and sign_in_required/sign_in_required_reason tell the user to run npx hyperiux login - every install needs a free account. Don't retry; ask the user to sign in.

Pro effects without a Pro subscription: metadata only, and source_locked explains the effect needs Hyperiux Pro - expected, not an error.

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:

  • "What does the dotted-grid effect need?" -> name="dotted-grid" (dependencies field)

  • "Show me the code for dotted-grid" -> name="dotted-grid", include_source=true

  • Don't use when: you don't have an exact slug yet - use hyperiux_list_effects first.

Error Handling:

  • Returns "Effect '' not found" if the slug doesn't exist - check hyperiux_list_effects for the correct spelling.

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:

  • "What kinds of effects does Hyperiux have?" -> call with no args

  • Don't use when: you already know the category slug and just want its effects - call hyperiux_list_effects directly.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct operation: browse/search the catalog, fetch one effect's full detail, and enumerate category slugs with counts. Descriptions go further than most servers by including explicit 'Don't use when' guidance pointing at the sibling tool to use instead, eliminating the list-vs-get overlap.

Naming Consistency5/5

All three tools follow a strict `hyperiux_verb_noun` pattern (list_effects, get_effect, list_categories) with a uniform server prefix. No mixing of camelCase, vague verbs, or divergent conventions.

Tool Count4/5

Three tools is on the lean side of the 3-15 sweet spot, but each earns its place for a read-only catalog browser: discovery, drill-down, and taxonomy. Nothing feels padded or redundant.

Completeness4/5

List + get + categories covers catalog discovery and detail well, including source retrieval, install metadata, and clear error/rate-limit paths. Minor gaps: no tier or dependency filter (agents must over-fetch and count client-side, as the description itself admits) and no dedicated install/setup tool, leaving that to the CLI.

Maintenance

ActivityActive
ResponsivenessSlow