Docs · 01 MCP

Plug naina into
your AI coding tool.

One command in your terminal. naina mcp starts the local server. Your AI tool talks to it over stdio — no wizard, no hosted endpoint, no context-switch. Your code, your machine, your call.

Localruns over stdio Privatecode never leaves Any clientClaude Code · Cursor · opencode One binaryeverything inside

01 — In your editor

One prompt. A whole running app.

Describe the product. Your AI tool calls naina, naina returns a tarball, you ship it.

The MCP server exposes naina's full surface as tools: build a design system, generate a homepage, scaffold the app, render the deploy config. Each call is deterministic — same input, same artifact.

No drift

Every component uses the system's tokens. The AI can't invent a stray hex code if you wanted it to.

No handoff

Design system, scaffold, and deploy config land together in one tarball.

No platform

naina.codes handles auth and billing. The binary does everything else.

{
  "mcpServers": {
    "naina": {
      "command": "naina",
      "args": ["mcp"]
    }
  }
}

claude code · acme.co • mcp · naina (local)

you

Spin up a fintech site called acme.co. Warm palette, Go + chi backend, deploy to vps-01.

claude

On it. Calling naina.

naina.create_system{ industry: "fintech", hue: 24 }✓ 24 tokens · 10 neutrals

naina.get_homepage{ industry: "fintech" }✓ hero · pricing · footer

naina.create_app{ stack: "go-chi" }✓ routes · db · 24 components

naina.get_deploy_config{ host: "vps-01", domain: "acme.co" }✓ deploy.yml

Tarball at ./acme.co.tar.gz. Want me to run kamal setup?

02 — Tools

The tools naina exposes.

naina.create_systemGenerate a complete design system from an industry and a hue. Returns 24 accents, 10 neutrals, the type scale, and the grid.→ tokens.css

naina.get_homepageReturn a pre-styled homepage for the chosen industry — hero, features, pricing, footer — wired to the system.→ home.html

naina.create_appScaffold a full Go + chi application — auth, db, routes, 24 web components. Ready to go run.→ tarball

naina.get_deploy_configRender a Kamal deploy.yml for your VPS — registry, hosts, healthcheck, secrets.→ deploy.yml

naina.list_componentsEnumerate the 24 components and their tag names — for the AI to pick the right one in context.→ json

naina.update_tokenRe-derive the system from a new seed (hue, scale, viewport bounds). The whole app shifts together.→ patch

Tools are deterministic. Same input, same output. The AI doesn't generate code — it picks which tool to call.

03 — Clients

Works with any MCP client.

Claude Code opencode Cursor Continue Codex CLI · planned Aider · planned

Setup

Two lines of JSON

Drop the snippet into your client's mcp.json. Restart. The tools show up as autocomplete. That's the entire install.

Transport

stdio · no ports

naina speaks the MCP stdio transport. No background daemons, no listening sockets, no firewall rules. Just a process the editor spawns when it needs it.

Sandbox

Local-first by default

Everything runs in the same working directory your editor sits in. Tarballs land next to the rest of your code, not on someone else's S3.

Ready to ship?
Wire it into your editor.

Two lines of JSON. One command. A running app at the end of the same prompt.