{ "name": "Luola", "version": "0.2.0", "description": "Build, edit, import, and publish complete websites from a prompt. Sites go live on *.luola.site in seconds.", "vendor": { "name": "Luola", "url": "https://luola.ai" }, "support_email": "support@luola.ai", "security_email": "security@luola.ai", "privacy_url": "https://luola.ai/legal/privacy", "terms_url": "https://luola.ai/legal/terms", "docs_url": "https://luola.ai/docs/mcp", "icon_url": "https://luola.ai/icon.svg", "mcp_endpoint": "https://mcp-dev.luola.ai/mcp", "transports": [ { "type": "http", "url": "https://mcp-dev.luola.ai/mcp" } ], "oauth": { "authorization_endpoint": "https://mcp-dev.luola.ai/authorize", "token_endpoint": "https://mcp-dev.luola.ai/token", "registration_endpoint": "https://mcp-dev.luola.ai/register", "metadata_url": "https://mcp-dev.luola.ai/.well-known/oauth-authorization-server", "legacy_bearer_prefix": "sb_live_" }, "tools": [ { "name": "list_projects", "title": "List Projects", "description": "List every website, landing page, and portfolio the user has built on Luola. Use when: user asks to show, list, or find their existing sites; \"what sites have I made\", \"näytä sivustot\", \"listaa kotisivut\", \"mitä sivuja mulla on\". Don't use when: user references one specific project — call get_project (status of one) or get_project_context (rich snapshot incl. domains/data-model/activity) instead. Returns each project's name, id, and live URL." }, { "name": "get_project", "title": "Get Project", "description": "Fetch the current status, files, and live URL of one Luola website project. Use when: user asks to check, inspect, or get status of a specific site; \"tarkista sivuston tila\", \"onko sivusto valmis\", \"what's the URL of my site\". After create_website / edit_website to confirm generation finished before publishing. Don't use when: user wants a rich snapshot with domains + data-model + activity → use get_project_context. Discovering project IDs → use list_projects first. Pre-reqs: project must exist (use list_projects to find IDs)." }, { "name": "create_website", "title": "Create Website", "description": "Build a complete website from a text prompt and publish it to a real URL on luola.site. Use when: user asks to make, create, or build a website / landing page / portfolio / business site / homepage / online store / marketing page / blog; \"kotisivut\", \"verkkosivut\", \"nettisivut\", \"kotisivut yritykselle\", \"sivusto\". Don't use when: user has HTML already → create_website_from_html. User has a sketch/mockup image → create_website_from_sketch. User has an existing URL to migrate → import_website. User wants to edit an existing site → edit_website (creative) or patch_site (mechanical). Initial generation produces up to 3 pages for speed (~2-3 min); add more later with edit_website. Set publish: true to go live automatically on *.luola.site." }, { "name": "create_website_from_html", "title": "Publish an HTML artifact as a live Luola site", "description": "Publish raw HTML (e.g. a Claude HTML artifact or any hand-written page) as a live website on *.luola.site in one call. Use when: user already has HTML — usually an artifact produced earlier in this chat — and asks to publish, deploy, host, put it online, make it a real website; \"julkaise tämä\", \"vie nettiin\", \"tee tästä oikea sivusto\". Don't use when: user has only a prompt → create_website. User has a sketch image → create_website_from_sketch. HTML is meant as a NEW page in an existing project → add_file_to_site. User wants edits to existing site → edit_website / patch_site. Accepts CSS and JS separately (auto-linked into /) and binary assets (images, videos, fonts) as base64. Returns project_id, preview URL, and live https URL. Total payload cap 2 MB; non-HTTPS external refs rejected to avoid mixed content." }, { "name": "create_website_from_sketch", "title": "Create Website From Sketch", "description": "Build a website from a sketch, drawing, whiteboard photo, screenshot, or mockup image (PNG/JPG/WebP). Use when: user has a visual design they want turned into a real live site; \"tee sivusto luonnoksesta\", \"kuvasta\", \"mockupista\", \"piirustuksesta\", \"Figma-kuvakaappauksesta\". Don't use when: user has no image, only a text idea → create_website. User has HTML output → create_website_from_html. User wants to migrate an existing live site → import_website. The sketch drives layout; optional text refines brand/tone; if name is omitted the AI derives one. Returns project_id + plan within seconds; background code generation finishes in ~1-2 minutes." }, { "name": "import_website", "title": "Import Website", "description": "Migrate an existing website to Luola while keeping its current domain. Scrapes the source site, analyzes design, rebuilds it as a Luola project; pairs with add_custom_domain so the user keeps acme.fi (and its SEO) on the new build. Use when: user wants to switch hosts, replace WordPress, leave Squarespace / Wix / GoDaddy / Shopify, redesign without losing domain or rankings, modernise an old site; \"tuo vanha verkkosivusto Luolaan\", \"säilytä oma domain\", \"vaihda hosting\", \"korvaa WordPress\", \"modernisoi sivut\". Don't use when: building from scratch with no source URL → create_website / create_website_from_sketch. User already exported HTML → create_website_from_html. Source is already a Luola project → edit_website / patch_site. Returns project_id; publishes to *.luola.site when publish: true. Combine with add_custom_domain afterwards to keep the original URL pointing at the new site. Note: heavyweight AI regeneration; expect 2-5 min per site." }, { "name": "edit_website", "title": "Edit Website", "description": "Modify an existing Luola website with natural-language instructions — add sections, rewrite copy, change layout, swap images, update styling, fix issues. Use when: user says change, update, modify, rewrite, add, remove, fix referring to an existing site; \"muokkaa\", \"päivitä\", \"lisää\", \"vaihda\", \"korjaa\". Creative edits where you can't precisely describe before/after text. Don't use when: change is a mechanical string/class swap with known before/after → patch_site (faster, no AI, ~1s vs 1-2min). Adding an entirely new file/page → add_file_to_site. Changing theme/colors/fonts only → configure_theme. Adding analytics/tracking → configure_integrations. Pre-reqs: project must already have generated files. Changes save automatically." }, { "name": "patch_site", "title": "Patch site files (find-replace)", "description": "Apply deterministic find-replace (string or regex) edits across a Luola site's HTML/CSS/JS. No AI call, runs in ~1s, never times out. Use when: user wants a mechanical change you can precisely describe as before/after text — colour class swaps, image src swaps, class renames, snippet removal or insertion, string substitutions; \"korvaa teksti\", \"vaihda väri\", \"swap string\". Don't use when: change is creative (new sections, layout changes, rewritten copy) → edit_website. Adding a NEW file/page → add_file_to_site. Changing theme tokens (colors/fonts) → configure_theme. Pre-reqs: target strings must exist in the site's files (no-op if no match). Changes write to D1 and re-upload to the live site immediately." }, { "name": "upload_media", "title": "Upload Media (image or video) to a site", "description": "Upload an image, photo, logo, banner, or video to a Luola site so it can be referenced as `./img/` in HTML. Use when: user asks to add, upload, or attach a picture, photo, logo, hero image, background, or video; \"lisää kuva\", \"lataa kuva\", \"lisää logo\", \"lisää video\", \"vaihda kuva\". Don't use when: file is HTML/CSS/JS/text → add_file_to_site. Changing existing image references in code → patch_site. Changing visual theme tokens (not actual files) → configure_theme. Pre-reqs: project must exist. Pass sourceUrl for files already on the web (preferred for >1 MB: Dropbox, S3, Imgur, GDrive) or dataBase64 for small inline bytes. Max 25 MB. Returns sitePath to reference in HTML." }, { "name": "optimize_tailwind", "title": "Optimize Tailwind (replace CDN with static CSS)", "description": "Speed up a Luola site by replacing the Tailwind runtime CDN (~124 KiB render-blocking script) with a pre-compiled /styles.css hashed to the classes actually used. Use when: user asks to improve PageSpeed, Lighthouse, Core Web Vitals, LCP, site speed, or page load; \"nopeuta sivustoa\", \"parempi suorituskyky\", \"PageSpeed-optimointi\", \"Lighthouse-pisteet\". Don't use when: user wants accessibility / contrast / build-error fixes → apply_quality_fixes. User wants a full performance audit before changing anything → audit_my_site. Pre-reqs: project must use Tailwind CDN (idempotent no-op otherwise). Safe to run repeatedly." }, { "name": "publish_website", "title": "Publish Website", "description": "Make a Luola website live at a public URL, or take it offline. Use when: user says publish, deploy, ship, go live, put it online; \"julkaise\", \"vie tuotantoon\", \"laita nettiin\", \"julkaise sivusto\". After create_website / edit_website / patch_site / configure_* when user wants changes visible to the public. Don't use when: site is still generating — poll get_project until generation_status=\"done\" first. Just-applied audit fixes the user hasn't reviewed — show them first. Pre-reqs: project must have generated files. Returns the live https URL on *.luola.site (or connected custom domain). Pass action: \"unpublish\" to take offline. If the API responds that a custom domain is not yet DNS/SSL-ready, surface the warning; only retry with overrideDomainWarnings: true after the user explicitly says publish anyway." }, { "name": "configure_integrations", "title": "Configure Tracking Integrations", "description": "Set up analytics and tracking on a Luola site — Google Tag Manager (GTM), Google Analytics 4 (GA4), Facebook Pixel — plus optional custom or pre- HTML snippets. Use when: user asks to add analytics, tracking, GTM, GA4, Facebook Pixel, conversion pixel; \"seuranta\", \"analytiikka\", \"lisää analytics\", or inject a custom