# Lanlan — Let's make the website you've been meaning to make.> Tell us what you do, who you do it for. We --- ## Lanlan — Let's make the website you've been meaning to make. (/) Lanlan — Let's make the website you've been meaning to make. Skip to content Lanlan . >_ Sign in Start Dashboard Lanlan . A website-making thing, made in Berkeley Let's make the website you've been meaning to make. Tell us what you do. We'll meet you wherever you are. Quick or thorough, your call. We'll get you a website. Connect See what people make I run a community-first coworking space in South Berkeley. We're called Our Space. Got it. Pulling that together now. ourspaceberkeley.org SOUTH BERKELEY COWORKING · EST. 2026 A workspace where you actually know the people around you. Community-first coworking for women, nonbinary folks, and femmes . Affordable, intimate, and rooted in real connection. Book a Call with Us → See Membership 35 Members max 24/7 Access $150/mo Sliding scale May 2026 Launch Made with Lanlan — A real customer site. ourspaceberkeley.org Real sites, made with Lanlan Real sites, real people. A Pilates studio. A coaching practice. A trinket box on a Berkeley sidewalk. A family cookbook. A park down the street. Made the way Lanlan makes them. immaqipilates.com For your studio practice A studio site as unhurried as the practice. Rehab-aligned Pilates for women in their 40s through their 80s. Deep forest green, gold line art, and room to breathe. immaqipilates.com → elizapatten.com For your coaching practice A coaching site that feels like you. Trauma-informed developmental coaching, in soft dusk colours and a quiet serif. Built in one conversation, now live at her own domain. elizapatten.com → rosebraillardteam.com For your real estate practice A realtor site with real art direction. Two realtors, 300+ career sales, a 20-year partnership. Warm, distinctive, nothing like a template. rosebraillardteam.com → lanimarsden.com For your work Lani Marsden Coaching & Consulting. Coaching for diverse voices, grounded in authenticity and somatic work. Their site, in their voice. lanimarsden.com → ✦ ✨ welcome to — Berkeley Trinket Trade stickers tiny figurines keychains pins friendship bracelets For the neighborhood Berkeley Trinket Trade. A take-a-trinket, leave-a-trinket box on a Berkeley sidewalk. Part of the worldwide Sidewalk Joy movement. A small thing made public. berkeleytrinkettrade.com → The Chester / Vestal Cookbook The Original Binder 124 recipes · 1981–2017 For the family voice A cookbook hand-typed by your family. 124 recipes typed by the Vestals and Chesters in the 1980s, photocopied and mailed in three-hole-punched binders. Now living online with the family voice preserved. chester-vestal-cookbook.lanlan.site → U N I C O R N M A Y A S L I R A I N B O W 🌈 Big Cat Trivia 🐆 Which rare cat lives at the highest elevations in the Americas? ⚠ HARD MODE ⚠ For someone specific Games for your kid, your group chat. A word search with a kid's friends' names rainbow-coded across the grid. A trivia game so brutally hard the group chat won't stop arguing. Made to delight one specific person. They count too. unicorn-word-search.lanlan.site → · big-cat-rainbow-trivia.lanlan.site → Willard Park Where Berkeley exhales — a small green hymn between the houses Derby & Hillegass For the place you love Willard Park — an ode to the park down the street. Not a business. Not a service. Just love for a place, made public. Built by neighbors, for neighbors. willard-park.lanlan.site → See more in the gallery → · Read the conversations behind these → Two ways in Both are free. Pick the one that feels right. No credit card needed for either. You can always switch later. Free I just need a site. Tell us what you do, who you do it for, and what your business is called. About five minutes. Then we'll make you a site. About twenty minutes from start to live. You don't have to know your colors or your brand. We'll figure those out as we go. Want the Lanlan Design Team later? It's right here. Start the quick way Free I want the Lanlan Design Team. About thirty minutes. Your Lanlan Design Team is three or four AI specialists — each thinking about your business from a different angle (brand voice, visual style, audience, copy). They talk to each other, push back on each other, and ask you questions along the way. The site you walk away with is the one you couldn't have described before we started. Here's how that works → Start the in-depth way You don't have to know what you want yet. We'll figure it out together. Made by six humans We made this for you. Lani CEO Juana Director of Strategy and Programs Jean Builder Britt Strategic Advisor Star Product Support W Will Technical Advisor Meet the team → When you're ready Let's go ahead and make the thing. Most people who use Lanlan have never used Claude before — that’s the AI we use under the hood. Here’s what to do. Start your site Read the questions we get × Connect your assistant Lanlan builds your site through a chat with your AI assistant. Pick the app you use. Claude claude.ai or desktop Claude Code in your terminal ChatGPT developer mode Cursor editor MCP Any other MCP client Cline, Windsurf, Zed, and more ← All apps Connect Claude Open Lanlan in Claude's directory. claude.ai/directory/connectors/lanlan-site ↗ Click Connect. Approve access to your Lanlan account when Claude asks — that's it. Not working? Open Claude's Customize → Connectors → Add custom connector and paste https://mcp.lanlan.site/mcp . The /mcp at the end is required. ← All apps Connect Claude Code Run this in your terminal. claude mcp add --transport http lanlan https://mcp.lanlan.site Start Claude Code and run /mcp . Choose Authenticate for lanlan . Approve access in the browser tab. Back to your terminal — you're connected. ← All apps Connect ChatGPT Turn on Developer mode. In ChatGPT: Settings → Connectors → Advanced → Developer mode. (Paid plans, on the web.) Open Plugins and add a server. Go to Plugins, click + , and paste this URL. https://mcp.lanlan.site/mcp Sign in to Lanlan when prompted. Approve access to finish. Not working? ChatGPT calls MCP connectors plugins , and they need Developer mode on a paid plan. ← All apps Connect Cursor Settings → MCP → Add new MCP server. Choose an HTTP server. Add the server with this URL. https://mcp.lanlan.site Approve access in the browser window. Cursor opens it automatically. ← All apps Any other MCP client Add a custom MCP server with this URL. Some apps call it a connector, integration, or tool server. https://mcp.lanlan.site Authorize Lanlan when prompted. Approve access in the browser window that opens. New to MCP? See the list of MCP clients . Try a green Preview · not saved × Tap to preview. Refresh to reset. Verdigris (live) #3F7A66 Fern #2F6B3D Original moss #3D5A2E --- ## For coaches — Lanlan (/coaches) For coaches — Lanlan Skip to content Lanlan . >_ Sign in Start Dashboard Lanlan . For coaches A homepage that sounds like you, not every other coach. You know your work. You know your people. Lanlan helps you say it on a page that feels yours — built around your niche, your voice, your rhythm. Start your site See how it works The shape of it Four stops, in plain language. No design vocab required. You bring what you know about your practice. Lanlan does the rest — and asks back when something isn't clear. To make this concrete, take Maya — a fictional somatic coach for therapists. She's a composite, not a real person. Here's how the four stops would look for her. 01 Share who you serve The first message is just you, in your words. Who you work with, what you help them with, how you want them to feel. A sentence or two is plenty to start. Don't have it all figured out? That's fine. Lanlan will ask. M Hi! I'm Maya. I'm a somatic coach for therapists — people who hold a lot for others all day. I work with body-based practices and breathwork, and the pace is slow on purpose. I want the site to feel grounded and warm — not clinical, not yoga-studio. People should be able to exhale a little when they land on it. Maya's whole first message. No prompt template, no setup. 02 A first homepage lands A few minutes after your first message, you have a real homepage — a live URL you can open on your phone and show your friend. maya-cole.lanlan.site SOMATIC COACHING · ESTABLISHED 2022 A grounded practice for somatic work. Body-based coaching for women in the helping professions. Slow, embodied, deeply attuned work. Book a Discovery Call → Maya's first draft. A live URL, sent within minutes. Not quite right yet — but enough to react to. 03 Refine in plain language Tell Lanlan what's off. No technical or design expertise needed. Things like: "The headline feels passive — make it more active." "Soften the green. I'm thinking seafoam, not forest." "Put a photo of me here, with a short bio next to it." "This whole section feels generic. Cut it." Lanlan changes it and shows you again. Repeat until it feels like yours. M I love the shape of it. But the audience is wrong — it's therapists specifically, not "women in helping professions." And the headline feels generic. Can it be sharper? Something about holding. And — I don't think the green is working. It's a little gym-locker. C Yes. Naming therapists directly. Most somatic sites go green, which means yours would blend in. Want to try clay instead? It's warmer and a bit more unexpected for the category. New headline draft: "A practice for the people who hold a lot." M Oh. Yes. That's it. maya-cole.lanlan.site SOMATIC COACHING FOR THERAPISTS · BERKELEY A practice for the people who hold a lot. Body, breath, slow. One-on-one work for therapists who need their own ground. Start a Conversation → M About Former licensed therapist. Twelve years of clinical practice before training in somatic experiencing. The work I do now is the work I needed when I was holding too much. Approach How the work goes. Body work. Paying attention to what the body's been holding — and what it wants to release. Breath. Tools to use between sessions, especially on hard days. Slow pace. We move at your nervous system's speed, not the schedule's. Working Together The 12-week container Six sessions, every other week. One-on-one. By referral or after a short call. 1:1 Quarterly small group Six therapists, four months, a different angle each time. Waitlist open. Group After a few rounds. The version that ships. 04 Or — bring in the Design Team If you'd rather slow down before any pixels move, ask for a design consultation. Lanlan brings in three or four AI specialists , each thinking about your business from a different angle — brand voice, audience, visual direction, conversion. They push back on each other and ask you questions before a single thing is built. Good for the moment your gut says: "I want to think first." V Voice specialist Maya — when you say "grounded," is that a word you'd use with your clients, or about them? It changes whether it shows up in the headline or stays a feeling underneath. A Audience specialist I want to push on who walks in first. Are these therapists already in burnout, or therapists who want preventative work? The headline reads differently depending on who shows up. M Hm. Honestly — both. But the burnout ones come first. The Design Team pushes back on each other — and on you — before a pixel moves. Meet the team → Want to see another example from a coach? Read Lani's conversation → Ready when you are Start with one sentence. Your first message doesn't have to be polished. Open Claude, say what you do and who you do it for, and see where the conversation goes. Not sure how to start? The sample prompts page has four you can paste in. Get started See sample prompts --- ## Lanlan / dev / architecture — what's actually under the hood (/dev/architecture) Lanlan / dev / architecture — what's actually under the hood Skip to content Lanlan . ☼ Sign in Dashboard See the handoff Lanlan . lanlan / dev / architecture What's actually under the hood. You've read the pitch. You're here for receipts. This page is the receipts — the data model, the deploy pipeline, the protocol layer, and the answer to the question every other platform's architecture page ducks: what happens if we want to leave? the primitives Six things a Lanlan site is made of. Files. Structured content. Form submissions. Live values. Page-level settings. Snapshots. Plus the brand guide that travels with all of them. Each is its own primitive with its own tools. primitive what's stored how you reach it where it lives files HTML, CSS, JS, images, fonts get_site_files , update_file , patch_file , edit_element object storage collections structured content with editable schemas (blogs, team pages, portfolios) collection (action-based) a database forms submissions to the site's contact forms form (action-based) a database live_data single live JSON values per key (counters, statuses, totals) live_data (action-based) a database page_settings per-page status, passwords, preview links, PWA toggle page_settings (action-based) a database snapshots every deploy, with point-in-time restore snapshots object storage brand design tokens — colors, fonts, voice notes — at /_brand/brief.md design_consultation , get_design_brief object storage (markdown file) Everything except the database tables is a file in object storage. The database holds metadata, schemas, and the things that need to be queryable. the pipeline What happens when you call update_file . The walk from tool call to live URL. Sub-15-second deploys, end to end. 01 tool call agent → mcp.lanlan.site Your agent serializes the call as JSON-RPC and sends it over Streamable HTTP. Single round-trip. 02 validate & write MCP server → object storage Server checks auth and the site pin, runs path validation, writes the new bytes to object storage. Snapshots the previous version in the same transaction. 03 deploy object storage → global CDN ⁰ Storage write triggers an edge deploy. Files land at every region's CDN node within seconds. 04 serve edge cache → live URL CDN edge invalidates, the new bytes serve. HTTPS automatic, no build step. ⁰ The CDN and object-storage stack are Cloudflare's. Happy to share specifics on a sales call — hi@lanlan.site . the protocol How the agent and the server talk. Streamable HTTP. JSON-RPC. No server-side state except the session and your default site pin. Everything else is one round-trip. tool call — agent → server { "jsonrpc": "2.0", "method": "tools/call", "params": { "name": "patch_file", "arguments": { "site_id": "33b69e87-...", "path": "index.html", "patches": [{ "find": "Welcome to my site", "replace": "Studio days. Wedding nights." }] } }, "id": 47 } response — server → agent { "jsonrpc": "2.0", "result": { "content": [{ "type": "text", "text": "{\"success\": true, \"patches_applied\": 1, \"deploy_id\": \"...\"}" }] }, "id": 47 } Stateful The session (auth) and the default site pin from select_site . Stateless Every tool call carries everything it needs. You can drop and resume mid-session and lose nothing. Transport Streamable HTTP. Older MCP clients on stdio need a transport bridge — most are on HTTP now. the escape hatches Five questions every other platform ducks. If you ever want to leave, here's exactly what that looks like. Answered honestly, including the question with the awkward answer. Can I export my sites? Yes. get_site_files returns every file. One bash loop and you have a folder of HTML/CSS/JS on your machine. No proprietary block model to translate. The bytes you wrote are the bytes you get back. The shape of an export — this is pseudocode for now. A real REST export endpoint is on the way; today this runs through your MCP client. # pseudocode — the MCP equivalent today, REST export coming for path in $(lanlan list-files --site $SITE); do lanlan get-file --site $SITE --path $path \ > "./export/$path" done Are the files mine? Yes. They're HTML, CSS, JS, and your media in standard object storage. Same shape any static site host expects. Drop them on Vercel, Netlify, S3, your own server. They work. Can I keep my domain? Yes. When you register_domain through Lanlan, the registration is in your name (or your client's) at the registrar. We're not the owner of record. To leave, you point the DNS somewhere else. We don't hold it hostage. Can I self-host the engine? Not today, honestly. The engine is small — a few thousand lines — but it's tied to Cloudflare's edge in ways that make a one-button self-host non-trivial. If you're a team with a strong reason to host it yourselves, write to us. We'll have a real conversation. What if Lanlan goes away? You keep what you built. Sites keep serving for the duration of the CDN cache. After that, you have your files (export above), your DNS (in your name), your Stripe account (in your client's name), and your form submissions (export them via the dashboard). No platform can promise to exist forever. We can promise that the day we stop, you don't lose your work. We want you to stay because the product is good, not because leaving is hard. The receipts hold up. Want to build? Two lines of config and you're connected to the engine. Install Lanlan Browse the recipes Keyboard × t focus the tool browser ? this overlay type lanlan open the console API esc close anything open There's also /.well-known/lanlan if you're the curious type. --- ## Lanlan / for developers — gallery (/dev/gallery) Lanlan / for developers — gallery Skip to content Lanlan . ☼ Sign in Dashboard See the handoff Lanlan . Made with Lanlan Build whatever you want. A bedtime tracker. A word search. A trivia game. A family cookbook. An ode to a park. The web used to feel like this — small, weird, made-by-one-person things. It can again. ★ ★ ★ 8:14 PM Lights out For your kid · or you Lights Out — a bedtime tracker. Two buttons and a timestamp. Hit one when they go down, one when they actually sleep. You see the pattern in a week. Built in an afternoon. lights-out.lanlan.site → U N I C O R N M A Y A S L I R A I N B O W 🌈 Big Cat Trivia 🐆 Which rare cat lives at the highest elevations in the Americas? ⚠ HARD MODE ⚠ For no reason at all Games made just to make. A word search with a kid's friends' names rainbow-coded across the grid. A trivia game so brutally hard the group chat won't stop arguing. Nobody asked for either. That's why they're good. unicorn-word-search.lanlan.site → · big-cat-rainbow-trivia.lanlan.site → The Chester / Vestal Cookbook The Original Binder 124 recipes · 1981–2017 For the family voice A cookbook hand-typed by your family. 124 recipes typed by the Vestals and Chesters in the 1980s, photocopied, three-hole-punched, mailed to relatives in binders. Now living online with the family voice preserved. chester-vestal-cookbook.lanlan.site → Willard Park Where Berkeley exhales — a small green hymn between the houses Derby & Hillegass For the place you love An ode to the park down the street. Not a business. Not a service. Just love for a place, made public. Built by neighbors, for neighbors. willard-park.lanlan.site → None of these need to make money. None need to last forever. Some live for one weekend. Others become the thing your family looks at for ten years. They all count. They're all real websites. They're all free. // every site here was built by talking to an MCP-speaking agent. then deployed. then forgotten about until someone wanted to show it to their kid. Built something with Lanlan? Send us the link. We'll feature it. Anything counts. The weirder the better. A trivia game your friends hate. A tracker for your dog's medications. A landing page for the band you started in 2008 and never quite gave up on. Email us --- ## Lanlan / for developers — build it, hand it off, walk away (/dev/) Lanlan / for developers — build it, hand it off, walk away Skip to content Lanlan . ☼ Sign in Dashboard See the handoff Lanlan . lanlan / for developers Build it, hand it off, walk away. Every site you ship ends the same way. It goes live. Then the emails start. Can you change this headline. How do I update the prices. The contact form stopped emailing me. You meant to ship a website. You accidentally signed up to be the IT department. Lanlan is the platform that lets you actually leave. + Mostly written for developers shipping client work, but every recipe holds for in-house builds and indie projects too. If you're shipping for yourself, you're just on both sides of the handoff. See the handoff How it works type lanlan anywhere · press t for tools · ? for shortcuts the arc 01 build You and your agent. Files are HTML/CSS/JS. Edits are surgical. Deploys land in 15 seconds. 02 invite One email. The client lands in a dashboard they actually understand — analytics, forms, snapshots, billing. 03 detach Drop yourself to admin. Or leave entirely. The site is theirs. So is the Stripe, the domain, and the form submissions. the other half Not all of it is MCP back-and-forth. Every site you build comes with this. Analytics, forms, snapshots, billing, sharing — the dashboard your client lands in when you hand it off. app.lanlan.site app.lanlan.site → — if you're already signed in, this drops you straight there. the handoff loop What this means in practice. Every bullet below is a specific email you do not get. The 7pm "I broke the homepage" email you don't get. Every deploy is auto-snapshotted. The client hits Restore. They're fine. The "the contact form stopped working" email you don't get. Forms ship with the platform. Submissions hit their inbox, not yours. Spam protection on by default. The "Google Analytics is asking me to verify something" email you don't get. First-party analytics. No tag to embed, no cookie banner to write, no GA console to log into. The "the domain expired" email you don't get. Domains are end-to-end. The DNS is in their name. The renewal notice goes to them. The "how do I take payments" email you don't get. Stripe is a primitive. The Stripe account is theirs, not a connected account routed through us. The "the new page I made looks weird" email you don't get. The site has a brand guide. The agent reads it on every edit. Six months from now, new pages still look like the site you built. the build loop Here's how it actually works. A real session, start to finish. Edit a client's site, ship it, hand it over. claude code — ~/clients/plumage ↻ replay Cursor, Codex, Gemini CLI, opencode, Cline, Continue, Zed — the install path looks similar. The engine doesn't care which agent's driving. the shape What's between you and a live site. Five hops. No proprietary glue between any of them. Architecture: you, your agent, MCP server, tools, engine, live site you natural language your agent Claude Code · Cursor · Codex · Gemini CLI · … MCP tool calls (JSON-RPC over HTTP) mcp.lanlan.site the MCP server dispatches to… 42 tools files · content · media · domains forms · sharing · analytics · SEO · … tools write to… the engine object storage · a database global CDN · automatic HTTPS deploy lands in <15s live site Open standards on every hop. MCP from agent to server. HTTP from server to engine. Files at rest. Nothing locks you in. the setup loop The stack you didn't have to assemble. Every Lanlan site ships with the standard internet plumbing already wired. Six things you'd otherwise spend an afternoon configuring. Analytics Embed GA4. Write a cookie banner. Set up consent. First-party. No tag, no banner, no console. Sitemap & robots Generate one. Update it on every page change. sitemap.xml and robots.txt regenerated on every deploy. llms.txt Hand-author it. Keep it in sync. Generated automatically. The agents reading your site know what's there. OG & meta tags Per-page boilerplate. A preview-card debugger tab open all afternoon. Per-page metadata is part of the page. Previews land right the first time. Custom domains Cloudflare/Vercel/Netlify console. DNS records. SSL provisioning. Redirects. Bought, connected, and HTTPS-served from one tool call. Snapshots & rollback Git ritual. Preview deploy chase. "Which build was the good one again?" Every deploy snapshotted. One click restores any point in time. None of this is the headline product. All of it is the reason a site ships in an afternoon and stays shipped. the protocol’s reach Today, agents. Tomorrow, anything that speaks HTTP. MCP is one door into the engine. The protocol allows others. Publishing surface: many possible inputs to one engine your agent (today) a script you wrote a GitHub Action a Slack command your internal tool a webhook the engine HTTP → deploy live Today, agents. The full handoff loop runs through any MCP-speaking client. Tomorrow, anything. A Slack command, a GitHub Action, a webhook from your CMS — if it can send an HTTP request, the protocol can carry it. files Your site, as a directory. Every Lanlan site is a folder of files. Here's this page's neighborhood. lanlan.site/ ├── _brand/ │ └── brief.md # the design tokens, in markdown ├── _partials/ │ ├── nav.html # shared across pages │ └── footer.html # shared across pages ├── css/ │ ├── style.css # one stylesheet, hand-written │ └── dev.css # this page ├── js/ │ └── dev.js # ~10kb, no framework ├── dev/ │ └── index.html # you are here ├── index.html # / ├── pricing.html # /pricing └── faq.html # /faq Most builders make you trust their proprietary block model. This is HTML. You can read it. There's no magic underneath. surface 51 tools, on the table. Press t to search, or just start typing. Hover any tool to see what it does. 51 / 51 Hover a tool, or press t and start typing. See the handoff. Build a site, invite a fake client, drop yourself to admin. Five minutes from now you've felt the whole arc. Install Lanlan Read the architecture Keyboard × t focus the tool browser ? this overlay type lanlan open the console API esc close anything open There's also /.well-known/lanlan if you're the curious type. --- ## Lanlan / dev / install — add the MCP server to your agent (/dev/install) Lanlan / dev / install — add the MCP server to your agent Skip to content Lanlan . ☼ Sign in Dashboard See the handoff Lanlan . lanlan / dev / install Pick your agent. Paste two lines. You're in. The MCP endpoint is https://mcp.lanlan.site . Streamable HTTP, no auth required for sign-in flows. Pick the client you use below. Claude Code Cursor Codex Gemini CLI 01 Add the MCP server. One CLI command. Run it in your terminal. claude mcp add --transport http lanlan https://mcp.lanlan.site copy 02 Start Claude Code and verify. Inside the agent, type /mcp . You should see lanlan listed as connected. /mcp copy 03 Build something. Just talk. Try this for your first session: Build a single-page site for my photographer friend Maya — homepage, contact form, bio. I'll invite her as the owner once it looks right. copy 01 Add the MCP server to your config. Open ~/.cursor/mcp.json (or create it) and add the lanlan entry. Project-scoped works too — use .cursor/mcp.json in the repo root. { "mcpServers": { "lanlan": { "url": "https://mcp.lanlan.site" } } } copy 02 Restart Cursor and verify. Open Settings → Tools & Integrations → MCP tools . The lanlan indicator should be green. 03 Build something. Open the agent panel. Try this: Build a single-page site for my photographer friend Maya — homepage, contact form, bio. I'll invite her as the owner once it looks right. copy 01 Add the MCP server to your config. Open ~/.codex/config.toml and add a [mcp_servers.lanlan] block. Note the snake_case key — Codex uses mcp_servers , not mcpServers . [mcp_servers.lanlan] type = "http" url = "https://mcp.lanlan.site" copy 02 Restart Codex and verify. Run codex mcp list . You should see lanlan listed. codex mcp list copy 03 Build something. Build a single-page site for my photographer friend Maya — homepage, contact form, bio. I'll invite her as the owner once it looks right. copy 01 Add the MCP server to your config. Open ~/.gemini/settings.json (or create it) and add the lanlan entry. Note the httpUrl key — Gemini uses that, not url . { "mcpServers": { "lanlan": { "httpUrl": "https://mcp.lanlan.site" } } } copy 02 Restart Gemini CLI and verify. Inside the agent, type /mcp to list connected servers. lanlan should be there. 03 Build something. Build a single-page site for my photographer friend Maya — homepage, contact form, bio. I'll invite her as the owner once it looks right. copy Other clients + The MCP endpoint is https://mcp.lanlan.site . Streamable HTTP. The exact config format varies by client — the URL is the same. opencode — opencode mcp add lanlan https://mcp.lanlan.site (or via ~/.opencode/config.json ). Cline — MCP Servers panel → Advanced MCP Settings. Add an mcpServers.lanlan entry with url: "https://mcp.lanlan.site" . Continue — ~/.continue/config.yaml . Add an mcpServers entry; same URL. Zed — Settings → AI → MCP Servers. Add a custom server with the same URL. If your client speaks Streamable HTTP MCP and isn't here, it'll work the same way. The endpoint is the same. Tell us if anything's missing — hi@lanlan.site . what you have access to now The doors that just opened. The dashboard app.lanlan.site — analytics, form submissions, snapshots, billing, sharing. Every site you build shows up here. 42 tools Sites, files, content, media, domains, analytics, SEO, sharing, version control, payments. See the inventory . Free to start The free tier covers up to five sites on lanlan.site subdomains with the full dashboard. Custom domains and sharing access are on the Pro tier — see pricing . if it doesn't work The four things that usually go wrong. The agent doesn't see lanlan after install. Restart it. Most clients only load MCP config on startup. If you added the server while the agent was running, fully quit and reopen it — not just close the window. JSON config errors. Trailing commas, missing quotes, unescaped backslashes on Windows paths. Validate the file in any JSON linter before troubleshooting deeper. Connection refused or timeouts. Check https://mcp.lanlan.site in a browser — you should see {"status":"ok","service":"lanlan-mcp"} . If that works but the agent can't connect, your client probably needs a version that supports Streamable HTTP transport (Cursor v0.48+, Claude Code current, etc.). Tool count limits. Cursor caps at around 40 active tools across all your MCP servers. Lanlan exposes 42. Disable the ones you don't reach for daily — delete_site , restore_site , feedback , probe_auto_forward . You won't miss them in normal building. Still stuck? hi@lanlan.site — a real human reads every email, usually within a day. Now you can build it, hand it off, and walk away. If the install worked, the rest of the loop is one prompt away. See the handoff Read the architecture --- ## Lanlan / dev / pricing — plain pricing, no surprises (/dev/pricing) Lanlan / dev / pricing — plain pricing, no surprises Skip to content Lanlan . ☼ Sign in Dashboard See the handoff Lanlan . lanlan / dev / pricing Plain pricing. No surprises. Two lanes, plus Full Service. Same plans as the warm side , one product, one set of prices, no dev-only SKUs. the plans What you get, what it costs. Free $0 /forever Real hosting, all MCP tools, no card. For solo work and indie projects. Up to 10 sites on *.lanlan.site Cloudflare Pages + R2 origin, served from the edge Forms, drafts, password gates, snapshots Pageview + Web Vitals analytics All ~40 MCP tools No credit card Start free recommended Pro $15 /mo Per-site subscription. The default for client work or anything on a real domain. $15/mo per site claimed (additive, not a flat fee) Custom domain — BYO or registered through us via Cloudflare Registrar Stripe payments + donations on the site Lanlan badge off Sharing & ownership transfer (built-in, not a connected-account hack) Get Pro Full Service Custom For mission-driven organizations and small businesses. Migrating in, running more than one site, or wanting someone else to build it. We migrate your existing sites to Lanlan Up to 100 sites + domains SSO Audit log + version history Dedicated support manager Custom contract + invoicing Get in touch the question every freelance/agency dev asks first Who pays after handoff? Both of you, at different stages. While you're building. Free covers it — 10 sites on *.lanlan.site . You only pay when you (or the client) want a custom domain, Stripe payments, or the badge gone. After you transfer ownership. The client owns the site, on their card, on their Pro subscription ($15/mo per site). Transfer is a first-class operation — no platform fees, no Stripe Connect routing, no shared subscription state. The clean handoff. Post-transfer, their billing applies: their card, their domain, their dashboard. You're not on the hook for their renewal. They're not on the hook for yours. Two people, two cards, one site that travels cleanly between them. the upgrade triggers Specifically, here's what costs money. Custom domains require Pro. Free is *.lanlan.site only. Removing the Lanlan badge requires Pro. Stripe payments & donations on the site require Pro. Multiple collaborators and unlimited scheduling, waitlists, and live data require Pro. SSO, audit log , and hands-on migration require Full Service . Everything else is on every plan. All MCP tools, the full dashboard, snapshots, analytics, SEO, forms, brand briefs, sharing & ownership transfer — none of these are tier-gated. the questions you'd ask next Plain answers. What if a client has two or three sites I built for them? Each claimed site is $15/mo, billed together: 2 sites = $30, 3 = $45. Past that, especially with multiple custom domains, point them at Full Service . What if I cancel and have an active client site? Sites you own become read-only — they keep serving, you can't edit. Client-owned sites (post-handoff) are unaffected. Reactivate within 30 days to restore edit access; after that, the site drops to Free tier (subdomain only). What happens to a site when its owner cancels and never comes back? Site drops to Free — stays live on *.lanlan.site but loses custom-domain routing and the badge comes back. Domains they registered through us stay theirs (registrant info doesn't change) and they can point them anywhere. Do I need a card to start? No. Free is really free. The card prompt only fires on Pro or a domain purchase. Can I get a refund if I upgrade and don't use it? 14 days, no questions. After that we'll talk. How do you handle taxes? Stripe Tax is on for paid plans. Receipts are tax-compliant per jurisdiction. Plain pricing. Real product. Start free. Go Pro when you have a real domain or a real client. Start free Talk to us Keyboard × t focus the tool browser ? this overlay type lanlan open the console API esc close anything open There's also /.well-known/lanlan if you're the curious type. --- ## Lanlan / dev / recipes — workflows for shipping client work (/dev/recipes) Lanlan / dev / recipes — workflows for shipping client work Skip to content Lanlan . ☼ Sign in Dashboard See the handoff Lanlan . lanlan / dev / recipes Twelve workflows. Real client work. Each recipe is a real situation a developer runs into when shipping a website — the prompt you'd give your agent, the tools it chains, and what you end up with. Same fictional client (Maya, photographer) the whole way down so you can read it as one project. + If you're shipping your own product or an in-house site, every recipe still works — you're just both sides of the handoff. Skip the invite the client step. Need to install Lanlan first? Two lines of config → 01 Hand off a finished site to a client. The site's done. The client should own it — the analytics, the form submissions, the Stripe, the domain. You want out of the loop without abandoning them. the prompt Invite my client maya@plumage.studio to the photographer site as a collaborator. Once she confirms, transfer ownership to her. I'll stay on as a collaborator for one week then drop off entirely. tools sharing(invite) → client confirms via email → sharing(transfer) → sharing(remove) What you end up with. Your client owns the site. They get the form submissions, the analytics dashboard, the Stripe revenue, the domain renewal notices. You can stay as a collaborator if they want help, or leave entirely. + Or your client can manage collaborators themselves from the dashboard once they own the site. 02 Import an existing site and rebuild it. Your client has an old Squarespace, Wix, or hand-built site they hate. You want their content as the starting point, not their layout. the prompt Pull everything from https://plumage-old.example.com — images, fonts, copy, structure. Build a new site at plumage-photography that uses that content but with a clean editorial layout. Same brand colors as the original. tools import_site → analyze_site → design_consultation(import) → update_files_batch What you end up with. A new site with the old site's content and brand DNA, in a layout you actually picked. The original site is untouched until you're ready to switch DNS. 03 Add a contact form that emails the client. The site needs a contact form. The submissions go to your client, not you. No Mailchimp, Formspree, or Netlify Forms in the picture. the prompt Add a contact form to the about page with name, email, and message fields. Submissions should email maya@plumage.studio. tools form(create, notify_email) → patch_file (drop