Hyperstack
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| reactflow_list_apisA | List all React Flow v12 APIs - components, hooks, utilities, and types |
| reactflow_get_apiA | Get detailed API reference for a specific React Flow component, hook, utility, or type. Includes props, usage, examples, and tips. |
| reactflow_search_docsA | Search React Flow documentation by keyword. Searches API names, descriptions, code examples, and tips. |
| reactflow_get_examplesC | Get code examples for a specific React Flow category |
| reactflow_get_patternB | Get an enterprise React Flow pattern with full implementation code. Patterns include store architecture, undo/redo, drag-and-drop, auto-layout, context menus, copy/paste, save/restore, DAG validation, keyboard shortcuts, performance, dark mode, SSR, subflows, edge reconnection, and more. |
| reactflow_get_templateA | Get a production-ready code template: custom-node (Tailwind + toolbar + handles + status), custom-edge (delete button + BaseEdge), or zustand-store (full store with selectors) |
| reactflow_get_migration_guideA | Get the React Flow v11 to v12 migration guide with all breaking changes, import changes, and type changes |
| reactflow_generate_flowB | Generate a React Flow component from a natural-language description. Returns ready-to-use TSX with proper imports. |
| motion_list_apisB | List all available Motion for React APIs (components, hooks, utilities) |
| motion_get_apiA | Get detailed API reference for a specific Motion for React component, hook, or utility. Includes props, usage, examples, and tips. |
| motion_search_docsA | Search Motion for React documentation by keyword. Searches API names, descriptions, and code examples. |
| motion_get_examplesC | Get code examples for a specific animation category |
| motion_get_transitionsA | Get the complete transition types reference (tween, spring, inertia, orchestration, per-value config) |
| motion_generate_animationA | Generate a Motion for React animation snippet from a natural-language description. Returns ready-to-use JSX. |
| lenis_list_apisA | List all Lenis smooth scroll APIs - ReactLenis component, useLenis hook, LenisRef and LenisOptions types. |
| lenis_get_apiA | Get detailed API reference for a specific Lenis API - props, options, usage examples, and tips. |
| lenis_search_docsA | Search Lenis documentation by keyword. Searches API names, descriptions, code examples, and integration patterns. |
| lenis_get_patternA | Get a complete Lenis integration pattern with full production-ready code. Covers Next.js setup, GSAP integration, Framer Motion sync, custom containers, accessibility, and navigation. |
| lenis_generate_setupB | Generate complete Lenis setup code from a natural-language description. Handles Next.js, GSAP, Framer Motion, basic React, and custom container scenarios. |
| react_list_patternsA | List all React/Next.js patterns by category |
| react_get_patternA | Get a React/Next.js pattern with full code example and anti-pattern |
| react_get_constraintsA | List all forbidden React/Next.js patterns and their reasons |
| react_search_docsB | Search React/Next.js patterns and constraints by keyword |
| echo_list_recipesA | List all Go Echo framework recipes. Optionally filter by category. |
| echo_get_recipeA | Get a specific Echo framework recipe with full working Go code, gotchas, and related recipes. |
| echo_list_middlewareA | List all available Echo framework middleware with their purpose and recommended chain order. |
| echo_get_middlewareB | Get detailed config and usage for a specific Echo middleware. |
| echo_search_docsB | Search Echo framework recipes and middleware by keyword. |
| echo_decision_matrixB | Given a need or requirement, get the recommended Echo pattern and recipe to use. |
| golang_list_practicesA | List Go best practices by topic and priority (P0=critical, P1=standard) |
| golang_get_practiceB | Get a Go best practice with good/bad code examples |
| golang_list_patternsA | List Go design patterns by category (creational, structural, behavioral, concurrency) |
| golang_get_patternB | Get a Go design pattern with idiomatic code |
| golang_get_antipatternsB | List all Go anti-patterns to avoid |
| golang_search_docsA | Search Go best practices and design patterns by keyword |
| rust_list_practicesC | List Rust best practices by chapter |
| rust_get_practiceB | Get a Rust best practice with code examples |
| rust_search_docsB | Search Rust best practices by keyword |
| rust_cheatsheetA | Quick Rust reference: ownership rules, error handling, clippy commands, and key patterns |
| design_tokens_list_categoriesA | List all 10 design token categories with descriptions and architecture layer |
| design_tokens_get_categoryA | Get full details for a design token category including CSS examples, rules, and gotchas |
| design_tokens_get_color_rampA | Get a color ramp (brand/neutral/pop) with all 11 OKLCH stops, semantic roles, and light/dark mode usage |
| design_tokens_get_procedureA | Get the step-by-step token system build procedure. Steps 1-8 cover the full production workflow. |
| design_tokens_searchB | Search design token documentation by keyword across categories, ramps, and procedures |
| design_tokens_get_gotchasB | List all common design token mistakes and fixes across all categories |
| design_tokens_generateA | Generate CSS token scaffolding from a description. Returns ready-to-use CSS custom properties. |
| ui_ux_list_principlesA | List all UI/UX principles by domain (typography, color, spacing, elevation, motion, accessibility, responsive, components) |
| ui_ux_get_principleA | Get full details for a UI/UX principle including examples, anti-patterns, and CSS examples |
| ui_ux_get_component_patternB | Get component pattern spec including variants, states, and sizing rules |
| ui_ux_get_checklistA | Get quality checklist for a UI/UX domain before shipping |
| ui_ux_searchA | Search UI/UX principles and component patterns by keyword |
| ui_ux_get_gotchasA | List all common UI/UX mistakes and fixes, optionally filtered by domain |
| designer_list_personalitiesA | List all 6 designer personality clusters with descriptions and exemplar names |
| designer_get_personalityA | Get full personality profile: description, exemplars, visual vocabulary, mode, and CSS example |
| designer_get_industry_rulesA | Get design rules for an industry: primary/secondary style, must-have features, never-use patterns, color mood, emotional target |
| designer_get_cognitive_lawA | Get a cognitive law: formula, key insight, UI applications, common violations, and academic source |
| designer_get_design_systemB | Get design system reference: signature, key insights, typography, color, spacing, reference code, and cross-system convergences |
| designer_get_composition_rulesB | Get visual composition rules: key rule, detail, applications, and violations |
| designer_get_interaction_patternC | Get interaction pattern: key rule, detail, best practices, and anti-patterns |
| designer_get_ux_writingA | Get UX writing guideline: key rule, evidence, do/don't examples |
| designer_get_landing_patternB | Get landing page pattern: key stats, best practices, and anti-patterns |
| designer_get_anti_patternsA | Get design anti-patterns filtered by category and/or industry |
| designer_resolve_intentB | Resolve a product description into a full design intent: industry, personality, style, mode, density, color mood, must-have/never-use lists |
| designer_searchB | Search across all designer knowledge: personalities, styles, industries, cognitive laws, design systems, composition, interactions, writing, landing, anti-patterns, and master principles |
| designer_generate_design_briefB | Generate a complete design brief for a product: resolves intent, then assembles visual theme, industry rules, style, cognitive laws, anti-patterns, design system inspiration, and composition rules |
| designer_get_page_templateB | Get section anatomy, component inventory, and applicable cognitive laws for a page type. Covers landing, dashboard, auth, settings, checkout, blog, docs, admin, profile, error-page, ai-chat, pricing, and onboarding. |
| designer_get_presetA | Get a complete, code-ready design token preset based on a real premium design system. Returns colors (OKLCH), typography (font, scale, weights, tracking), spacing, radius, shadows, motion, and CSS example. Available presets: linear, stripe, vercel, apple, carbon, shadcn, notion, supabase, figma. |
| designer_list_presetsA | List all available design presets - complete, code-ready design token configurations based on real premium design systems (Linear, Stripe, Vercel, Apple, Carbon, shadcn, Notion, Supabase, Figma). |
| designer_get_font_pairingA | Get curated font pairings filtered by mood (technical, elegant, friendly, editorial, bold, corporate, playful, luxury, startup, minimal) and/or industry. Returns heading + body + mono fonts with weights, tracking, line-height, Google Fonts import, and rationale. 21 pairings available. |
| designer_generate_implementation_planA | Parse a DESIGN.md into its 10 sections and generate a structured implementation plan. Each section becomes one or more tasks with exact MCP calls (shadcn_get_component, motion_generate_animation, design_tokens_generate, etc.) and self-review assertions. Caller reads DESIGN.md locally and passes the full text as design_md_content. |
| designer_verify_implementationA | Verify implementation code against its DESIGN.md contract. Runs pattern checks for anti-patterns (AI purple, font-weight 500 everywhere, cold shadows, etc.), verifies OKLCH tokens present, checks for prefers-reduced-motion, and reports per-section compliance. Use this before ship-gate. Caller reads files locally and passes contents inline. |
| shadcn_list_componentsA | List all curated shadcn/ui components (Base UI edition). Optionally filter by category: button, input, card, dialog, dropdown, tabs, table, form, navigation, feedback, overlay, data-display. |
| shadcn_get_componentA | Get full details for a shadcn/ui component: base primitive, data-slots, variants, sizes, usage example, and which other components it pairs with. Uses curated reference data. |
| shadcn_get_rulesA | Get the architectural rules and mandatory checklist for shadcn/ui (Base UI edition). Call this before proposing any new component or modification. |
| shadcn_get_snippetA | Get a usage code snippet for a shadcn/ui component. Returns the canonical example showing variants, sizes, and composition patterns. |
| shadcn_get_compositionA | Get shadcn/ui component composition for a specific page type. Returns which components to combine per section with rationale. This is the bridge from designer's page templates to concrete implementation. Use after designer_get_page_template. |
| hyperstack_setupA | Identify current IDE/CLI environment and generate a tailored MCP configuration patch for Hyperstack. |
| optimizer_match_problemA | Match a problem description (or what the code does) to likely algorithmic classes and the candidate techniques to consider. Returns the menu to scan; the implementation is not shipped on purpose - web search the technique you pick. |
| optimizer_get_techniqueA | Get a technique's complexity, when it fits, the naive smell it replaces, and the web-search query to fetch its authoritative implementation. The catalog ships no code by design - algorithms are stable; verify the impl and exact complexity against a real source, not memory. |
| optimizer_list_techniquesA | List the technique menu, optionally filtered by class. Each row is name + complexity + when to reach for it. No implementations - this is the recall aid. |
| optimizer_list_classesA | List the algorithmic problem classes in the catalog with how many techniques each holds. The taxonomy to orient on before matching a problem. |
| optimizer_searchA | Free-text search across the technique catalog (name, class, when-to-use, and the naive smell it replaces). |
| product_manager_get_four_risksA | The four product risks every build must address before shipping (Cagan/SVPG): value, usability, feasibility, viability - with which role owns each. The PM owns value and viability. |
| product_manager_get_jtbdA | Jobs-To-Be-Done framing (Christensen): a job is progress-in-context across functional/emotional/social dimensions, plus the Four Forces switching rule. Use to reframe a feature request as the underlying job. |
| product_manager_get_discovery_rulesA | Continuous-discovery rules (Torres): weekly customer contact, never ask 'what do you want', elicit past-behaviour stories. Use before claiming a build is customer-grounded. |
| product_manager_get_anti_patternsA | Codifiable PM red flags (Cagan, Doshi): feature-factory, reactivity, viability-avoidance, execution-misdiagnosis, opinion-requirement. Use to flag weak product reasoning. |
| product_manager_get_strategy_rulesB | Product-strategy rules (Cagan): focus on 2-3 levers, saying no is the act of prioritization, a long list is a non-strategy. Use to cut scope. |
| product_manager_opportunity_vs_solutionA | Returns the Torres opportunity-vs-solution rubric (the test + reframe examples) for YOU to apply - it does not classify for you. Use to reframe a solution-shaped request into the underlying need. |
| product_manager_validate_job_statementA | Returns the 7-point JTBD job-statement criteria (Christensen/Ulwick) for YOU to judge a statement against - it does not pass/fail for you. Use to sharpen a vague job into one with context + progress. |
| product_manager_score_riceA | Compute a RICE prioritization score = (Reach x Impact x Confidence) / Effort (Intercom). Confidence is 0-1. Use to rank competing initiatives. |
| product_manager_resolve_product_decisionA | The PM gate. Supply YOUR value and viability assessments for the proposal; returns a real verdict - PASS (both addressed), BLOCK (net-new build with a PM-owned risk unaddressed), or ADVISORY (tweak). PASS is earned by actually assessing value AND viability, not automatic. The judgment is yours; this enforces that you made it. |
| product_manager_get_prioritizationB | Prioritization frameworks beyond RICE: MoSCoW (release scoping), Kano (basic/performance/excitement), ICE, WSJF / cost-of-delay, and opportunity scoring (importance vs satisfaction gap). Use to decide what to build and in what order. |
| product_manager_get_decision_toolsB | Decision-making toolkit: Type-1/Type-2 (reversible vs one-way-door) decisions, the 70% rule, pre-mortems, disagree-and-commit, decision records, and decision-vs-outcome quality. Use to make and document calls under uncertainty. |
| product_manager_get_mvp_scopingA | MVP & scope-cutting: what an MVP really is, the Riskiest Assumption Test, vertical slicing / walking skeleton, story slicing, the cut test, and de-risk order (value->usability->feasibility). Use to cut a build to its thinnest valuable slice. |
| product_manager_get_roadmappingA | Roadmapping: Now/Next/Later horizons, outcome-based (not feature-based) roadmaps, theme-based organization, and GIST. Use to communicate direction without faking date precision or sliding into a feature factory. |
| product_manager_get_metricsC | Product metrics: North Star metric, One Metric That Matters, OKRs (outcomes not tasks), Google's HEART, AARRR, and input-vs-output / vanity-metric traps. Use to define what success is measured by. |
| product_manager_get_product_senseB | How to develop product sense (Jules Walter, Julie Zhuo): customer immersion, product teardowns/critiques, principles-first learning, and closing the predict/outcome loop. The deliberate practice for building product judgment. |
| marketing_get_positioningA | Positioning framework (April Dunford): the 5 components in order (competitive alternatives -> unique attributes -> value -> target -> category) + the 3 positioning styles + a positioning-statement template. Use FIRST, before any messaging or copy. |
| marketing_get_messagingB | Messaging frameworks: value-proposition canvas (jobs/pains/gains), StoryBrand SB7 (customer is the hero), strategic narrative (Raskin - story = strategy), and the message hierarchy. Use after positioning is set. |
| marketing_get_copywriting_formulasA | Copywriting formulas with fill-in templates: PAS, AIDA, BAB, FAB, PASTOR, 4 Ps, the 4 U's. Use to structure any headline, ad, landing page, or email. Apply the formula yourself - this supplies the templates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| cheatsheet | React Flow v12 quick reference cheatsheet |
| cheatsheet | Motion for React quick reference cheatsheet |
| lenis-cheatsheet | Lenis React quick reference cheatsheet |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/orkait/hyperstack'
If you have feedback or need assistance with the MCP directory API, please join our Discord server