Hype StackHypeStack

Search

Search the packs, templates, docs, and pages

Model Context Protocol, over stdio

Ask your editor
to build it for you.

The installer is also an MCP server. Your agent searches the catalog, plans the install, and writes the files, from a local process on your own machine.

Read the docs
Works inCursorCodexClaude CodeT3 CodeVS Code

one sentence in cursor

0

files written in your repo

the installer, in your editor

Features install where you already work.

A local MCP server

The installer runs over stdio on your machine. No cloud in the loop, no code leaving your disk.

It plans before writing

Searches the catalog, checks your license, shows the whole plan, and asks before touching a file.

hype-stack mcp

search_catalog · found pack-billing-stripe

plan_install · 75 files, asks first

add_packs · writing to your repo

Any MCP editor

Cursor, Codex, Claude Code, T3 Code, VS Code: one setup command each, approved once in the browser.

The files are yours

Real source lands in src/ across your six apps, committed like anything you wrote yourself.

install, from the editor
"Add Stripe billing"you, in cursor

mcp

plans, asks, writes
75 filesin your repo, yours
The whole pitch

You ask in the editor. Your app answers.

A real capture: the notifications pack, installed by an agent over MCP, running in the app.

CursorMCP

Add in-app notifications

hype-stack mcp

  • Found the notifications pack
  • Planned 63 files, zero conflicts
  • Wrote them into your repo
Ask for the next feature
local process, nothing leaves your machine
Your app, afterlocalhost:3000/notifications
The notifications feature running in the app after the agent installed it
Setup

One command. It does the rest.

Pick an editor, run the command, approve once in the browser. Nothing to paste, no separate login.

hype-stack mcp install

Then, in Cursor

Add billing with team seats

No browser on that machine: pass a key from the API keys page with --token

Shows as failed in the editor: npx @hype-stack/cli@latest mcp check --editor cursor

The tool surface

It looks first. It writes only with a plan.

Seven tools read. Four write, and each one shows the plan and waits for your yes.

Reads

cannot change a file
  • Finds the right featuresearch_catalog
  • Checks before it buildsplan_install
  • Knows what you already haveinspect_stack
  • Spots the missing keysenv_status
  • Knows who you areauth_status
  • Teaches the pack formatpack_authoring_guide
  • Checks a pack you wrotevalidate_pack
every write
  1. shows the plan
  2. →you say yes
  3. →then it writes

Writes

shows the plan, then your call
  • Starts a new appcreate_application
  • Adds a featureadd_packs
  • Applies a whole templateapply_template
  • Boots the databasessetup_project
No tool forbuy a packrun a migrationtouch files outside the project
What you get

Set it up once. Every project gets faster.

Your agent stops guessing at features and starts installing finished ones. That is days of build time returned per feature.

  • 63

    Files written from one sentence

    The notifications pack: frontend, backend and admin, planned then written.

    billing
    47
    notifications
    63
    collaboration
    75
    files per ask

  • minutes

    For a feature that takes days by hand

    Finished, tested packs instead of an agent improvising billing from scratch.

    agent improvises itdays
    agent installs the packminutes

  • 0

    Trips out of the editor, ask to running app

    The plan, the files and the result land in the chat you already have open.

    terminal session
    docs tab
    your editor chat

Prefer the terminal? Same binary, see the CLI. Want your agent held to the project's conventions? That is the rules and lint setup.

Model Context Protocol

Your editor can install features

Five tools only look. Three write, and they show the plan first.

Every editor

Stay in the window

Cursor, Codex, Claude, T3 Code, VS Code. Same server.

Cursor

Codex

Claude

T3 Code

Copilot

Read first

It surveys before it builds

Catalog, license, and your stack, before a file is touched.

01

Look around

search_catalog, inspect_stack

02

Check access

plan_install, auth_status

03

Write source

add_packs, same files as the CLI

Then writes

Source in your repo

Same installer as the CLI. Same files.

add_packs · via mcp

A apps/frontend/…/billing/

A apps/backend/…/billing/

M prisma/schema.prisma

✓ ready to review

Guardrails

It cannot spend your money

Missing a license? It names the pack and links it.

  • Read tools never write
  • Paid packs need a credential
  • Same binary as the CLI
Within reach

What one ask can install.

The feature surface behind those eleven tools. Your agent installs finished features instead of improvising them.

Feature packs

  • Ready-made screens
  • API & database included
  • Admin tools included
TypeScriptHonoPrisma

Automatic SDK

  • Generated from API routes
  • Typed frontend client
  • Catch breaking API changes
HyperFetchHonoTypeScript

MCP server

  • Search feature packs
  • Review install plans
  • Install from your editor
CursorClaudeGitHub Copilot

AI-ready code

  • Feature-based structure
  • Small, focused files
  • Works with your AI editor
CursorClaudeGitHub Copilot

Agent instructions

  • 13 coding rules
  • 8 agent skills
  • 4 custom lint rules
CursorClaudeGitHub Copilot

Install previews

  • See every planned file
  • Approve before install
  • Review source changes
TypeScript

Ask your editor.
Own the result.

works incursor · codex · claude code · vs code

Feature packs to grow with

Every pack ships real source code: frontend, backend, and admin surfaces where the feature needs them. Add them when you need them, one command each.

FeatureBilling (Polar)Polar integration, subscriptions, billing flows, and an admin revenue widget.Polar checkout & portalMerchant of recordFeatureTeamsTeam workspaces with members, roles, icons, and email invitations on top of your starter.Team workspacesMember rolesFeatureNewsletterNewsletters end to end: a hosted archive, signup surfaces for web and mobile, a minimal block studio with a full custom-HTML mode, scheduling, and open/click analytics built for sponsor reports.Block email studioPublic signup + unsubscribeFeatureBilling (Lemon Squeezy)Lemon Squeezy integration, subscriptions, billing flows, and an admin revenue widget.Lemon Squeezy checkout & portalMerchant of record
See all 19 packs

Questions, answered

Yes. Everything lands as plain source in your repository: frontend, backend, admin, database schema. There is no runtime dependency on us and nothing phones home.

Add it once. Use it on every project.

Installed globally, the tools are there even in an empty folder. So your agent can create the project too.

See what it can installRead the MCP docs

local process / 6 of 11 tools read-only