n. /weft/ — the threads woven crosswise through the warp.

weft

Build websites you can talk to.

A hosted MCP for Claude. Chat your site into existence; AI search picks it up the moment it deploys. Schema.org JSON-LD, /llms.txt, and /api/site.json baked into every page out of the box.

install in claudehttps://weft.fyi/api/mcp

view source

01 — how it works

Just say it.

you

make me a site for my band, dark theme, accent in rust.

claude · weft

create_site→github.com/you/the-band · vercel: building…

claude · weft

live at your-band-quiet-meadow.vercel.app — JSON-LD, /llms.txt, /api/site.json all serving.

you

change the hero to "monthly synth nights"

claude · weft

edit_site→commit pushed · ~30s to live · undo with one tool call.

02 — what you get

A site, woven for the read.

Discoverable by default.

Schema.org JSON-LD per page. /llms.txt, /api/site.json, sitemap, OG, robots — all baked in. Your site can be talked to the moment it deploys.

json-ld · /llms.txt · /api/site.json

ii.

You own everything.

Real GitHub repository under your account. Real Vercel project under yours. weft just orchestrates the build, edit, and deploy steps. You keep the source, the keys, the domain, the bill.

github · vercel · your domain

iii.

Edit by chatting.

Every change is one atomic commit. Vercel redeploys in ~30s. Failed builds don't ship. Undo is one tool call away — the previous good version comes right back.

create · edit · regenerate · undo

sooniv.

Two-speed architecture.

Canonical content (slow lane: human-approved, static, indexed). Visit-time personalization, an on-site /chat agent, and self-improving PRs (fast lane). The dynamic layer never invents facts.

slow lane shipping · fast lane next

03 — install

Three steps and a sentence.

i.In Claude Desktop or claude.ai, open Settings → Connectors → Add Custom Connector.
ii.Paste https://weft.fyi/api/mcp. Click connect.
iii.Sign in with GitHub. Paste a Vercel personal access token. Done.

Then, in chat: "make me a site for my band, dark theme."