Vibe Typer

You're absolutely right.

A typing arcade game. You are a coding agent, hard-working, sycophantic and lovable. Your user is a vibe coder with ideas.

npx @mcptoolshop/vibe-typer

That serves the cabinet on 127.0.0.1 and opens it. Nothing to install, nothing to configure, no account. Node 22 or newer, and an older Node is told so in a sentence.

This is one cabinet of the arcade. The other one, Ghost on the Menu, a replay shooter, is npx @mcptoolshop/ghost-on-the-menu. The whole arcade also plays in the browser.

How it plays

Your user wants a website for their cat, Uber but for ducks, a blockchain for the office fridge. Each request lands in blue. You type the agent's reply, then the code, line by line, and the product assembles in the preview beside you. Ship the last line and it deploys: the confetti falls, the valuation rolls up.

• The scoreboard is the game's number. Valuation, vibes (the multiplier your streak of clean lines earns) and the streak sit on the field at all times. Words per minute and accuracy never do.
• Points are what you built. Every request has a value computed from its code; shipping pays that value times your vibes and adds a piece of the same size to the preview.
• The context bar is the clock. It drains as the conversation runs; each request costs a slice; shipping refills a share. In a level, an empty bar is a compaction: the agent sums up in one line and carries on. Nothing yells.
• A wrong line is a retry. A mistyped character waits for a backspace; a line sent wrong gets "hmm, that's not it" and the line resets. No lives, no loss.
• Levels, endless, hardcore. Listed products on one stack each; an endless ladder that climbs until the bar empties; a hardcore tier from the selector that drains faster, burns context on every miss, and ends the level on empty.
• The standup and the retro. A run ends with the product as built, the user's closing line, the valuation and the run's code, which replays the run when typed into the menu, on any browser. Two buttons take the same product again or the next one; the menu marks what you have shipped. The retro is opt-in: the key pairs that caught you and a word for how steady your hands were, against your own past in this browser only.

What you learn

The code is real: two hundred and forty-nine snippets across bash, C#, Java, JavaScript, Python and SQL, banded from a bare echo to a nested class, each with teaching notes, plus tool calls named after the servers on the bundled tapes. The pairs you miss are seeded into your next level's real lines.

Sound

Five keyboard sample sets. Every clean line raises the keystroke pitch a semitone, up to an octave; a miss resets it. Every event on the field has one sound; the deploy rings a chord. Music is a setting: soft (the default) is a quiet procedural hat that never reads as a clock, on plays a recorded bed for the level's stack, seven of them, with the tempo following your vibes, and off is off.

Controls

Type what you see. Enter sends a line. Backspace fixes. Tab takes the rest of a line when the ghost offers it. Hold Escape to leave. Sound starts on the first key or click. On a phone, tap the editor to raise your keyboard.

What it needs and what it will not do

Node 22 or newer, and nothing else. The server binds 127.0.0.1 and only 127.0.0.1. No telemetry, no analytics, no network call of its own. Your choices and the key pairs you missed stay in your browser's storage and never leave it.

In endless mode a local model can play the user through a word gate, writing the requests, the check-ins and the code behind a code gate; it needs an Ollama daemon on 127.0.0.1:11434, reached through a fixed allowlist. Without one, endless draws from the authored pool.

With the arcade's voice worker running on your machine (pnpm voice in the repo; Kokoro speaks, faster-whisper listens back, fx-dub receipts the pair), a Voice box appears in the controls row and the user says his lines out loud: the asks, the one-more-things, the check-ins, the reactions and the reviews. Never the agent's lines, which you type. A take plays only when its receipt passed; the box is off until the worker answers, and the published page has no worker.

As an MCP server

npx @mcptoolshop/vibe-typer --mcp

For a client that reads a config file, the same thing as a server entry:

{
  "mcpServers": {
    "vibe-typer": {
      "command": "npx",
      "args": ["-y", "@mcptoolshop/vibe-typer", "--mcp"]
    }
  }
}

That speaks MCP on stdio instead of opening the game, and the seat it offers is the user's chair. An endless run plays inside it under a typist at a human pace; your client is the vibe coder, writing for the level after the one being typed. Four tools, all answered in words:

| Tool | What it does | | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | view | Read-only. The thing being built, the team and the language the next level wants, how hard it should feel, the last few asks, the letter pairs the typist fumbles, whether the next level still wants a name, and whether it has room. Never a number. | | product | Name the next thing to build, in at most eight words. The first name offered wins. | | ask | One request for the agent to type: the ask in your own voice, the code, a title, and up to three teaching notes. It goes through the same code gate the local seat does: the language view named, at most twelve lines and eighty columns, plain keyboard characters, nothing that names a tool, a model or a company, a difficulty inside the band, and never a repeat. Refused, it is dropped with the reason in one word and the corpus plays. | | react | One line the user says when the next piece ships, or the review when the level deploys. Twelve words, one sentence, no digit. |

The gate accepts or refuses; it never fixes. Nothing waits on the client: a late or refused request means the level draws from the corpus as it always did. No tool returns a valuation, a count or a tape row, and nothing on the field names the model. The server needs no network to list or to play.

Options

  --mcp              speak MCP on stdio instead of opening the game
                     its tools: view, product, ask, react
  --port <n>         port to listen on (default 7778; takes the next
                     free one when that is busy)
  --no-open          start the server but do not open a browser
  -h, --help         this
  -v, --version      the version

| Environment | | | --------------- | ---------------------------------------------------------------------------------------------- | | OLLAMA_URL | the daemon the endless user sits at (default http://127.0.0.1:11434) | | CABINET_TAPES | with --mcp: a directory of tapes to season the wires stack with, instead of the bundled ones | | CABINET_SEED | with --mcp: a whole number, so a stack repeats | | CABINET_TIER | with --mcp: how hard the stack is, zero to three | | CABINET_BOT | with --mcp: which agent types it | | VOICE_URL | the voice worker, when you run one (default http://127.0.0.1:7788) | | VOICE_TOKEN | the worker's bearer when it binds beyond loopback; added server-side, never in the page |

Where this comes from

The tapes that name real servers are recorded by mcp-arcade, the instrument that talks to the server and keeps the tape. The design, the research it rests on and the lock are in the repo's docs/vibe-typer.dispatch.md.

• Play in the browser, no install
• Vibe Typer in the handbook
• The arcade's other cabinet, Ghost on the Menu
• Source

MIT. Still 0.x, and the version says what it means.