Spun

Get started — from sign-up to a live site

Your site is already live at <your-handle>.myspun.ink — the address in your sign-up email. Right now it shows an under-construction page, because a new spun.ink site starts genuinely empty: no sample pages, no starter theme, nothing to delete. Your AI agent writes all of it.

  1. Confirm your email
  2. Connect your agent
  3. Describe your site
  4. Approve, and publish

1Confirm your email

Click the link we sent you. It unlocks publishing — without it your agent can still author, restyle and preview everything.

It is also the moment the contract is concluded, which is why a person has to click it and not an agent: by confirming your address you accept the Terms of Service. See our Privacy Notice for information about how we process your personal data. Two things in the Terms are worth knowing before you click: spun.ink has no web page for editing your site, and when your agent reads a form submission your visitor’s data goes to your agent’s AI vendor.

Nothing in the inbox?

Check the spam folder, then ask your agent to run resend_verification_email.

2Connect your agent

There is no dashboard to log into — on spun.ink your AI agent is the one who builds. Pick your client below and connect it, with your token in place of <token>.

In your terminal

claude mcp add --transport http spun https://spun.ink/mcp \
  --header "Authorization: Bearer <token>"

Or, in a project folder

.mcp.jsonjson
{
  "mcpServers": {
    "spun": {
      "type": "http",
      "url": "https://spun.ink/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

claude mcp list shows spun as connected.

Claude Code documentation
~/.cursor/mcp.jsonjson
{
  "mcpServers": {
    "spun": {
      "url": "https://spun.ink/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Cursor Settings → MCP lists spun with its tools. A project-scoped .cursor/mcp.json works the same way.

Cursor documentation

In your terminal

code --add-mcp '{"name":"spun","type":"http","url":"https://spun.ink/mcp","headers":{"Authorization":"Bearer <token>"}}'

Or, per project

.vscode/mcp.jsonjson
{
  "inputs": [
    { "type": "promptString", "id": "spun-token", "description": "spun.ink bearer token", "password": true }
  ],
  "servers": {
    "spun": {
      "type": "http",
      "url": "https://spun.ink/mcp",
      "headers": { "Authorization": "Bearer ${input:spun-token}" }
    }
  }
}

The MCP servers view lists spun; in agent mode its tools appear in the tool picker.

VS Code documentation

In your terminal

export SPUN_TOKEN=<token>
codex mcp add spun --url https://spun.ink/mcp --bearer-token-env-var SPUN_TOKEN

Or, in the config file

~/.codex/config.tomltoml
[mcp_servers.spun]
url = "https://spun.ink/mcp"
bearer_token_env_var = "SPUN_TOKEN"

codex mcp list shows spun with auth Bearer token. The token stays in your environment, never in the file.

Codex CLI documentation

Three values, nothing else

endpoint     https://spun.ink/mcp
header       Authorization: Bearer <token>
transport    HTTP (JSON-RPC 2.0 over POST, no SSE)

Ask your agent to name spun.ink's tools. The server sends its instructions on connect, so a connected agent already knows what it can do.

The agent guide at /docs
About your token

It was shown once, right after sign-up. It is full access to your site — treat it like a password. Lost it? /recover emails a link that rotates it and reveals the new one.

3Describe the site you want

Plain words, no briefing document. The more concrete you are about the pages, the audience and the tone, the less back-and-forth it takes. Copy this starter prompt:

Build my site: a home page for our two-person carpentry workshop in Vienna,
a page about our work with room for six photos, and a contact page.
Calm and warm, not corporate. Show me a preview before you publish anything.

4Approve, and it is live

Your agent hands you a preview link — a real page in a browser, not a wall of settings. Say what to change; it changes it. Say publish, and your address stops saying under construction.

  • Publishing is a boundary, not a switch. The public page changes only when your agent publishes, so nothing half-finished is ever visible.
  • Every publish is kept. Ask for the bold version — you can always go back.

Where to go from here

  • Just keep asking. New page, new section, a different look, a blog post — the same conversation every time. Nothing you build here needs maintaining, updating or hosting.
  • Your own domain. On a paid plan your agent points it at spun.ink and the certificate is issued automatically — see /pricing.
  • The deep reference is /docs — written for agents, not for you. Point yours there if it wants the full tool surface.