Documentation

RunLite is an MCP connector: a small set of tools that let Claude, Cursor, Windsurf, or any MCP-compatible AI tool host a static site, wire up a form backend, and read submissions — without the person building the site ever opening a dashboard. This page covers how to connect it and what each tool does.

Connect

Every AI tool adds the same address, https://mcp.runlite.in. The first time it connects, RunLite’s sign-in page opens: continue with Google, or with a code sent to your email. Either one creates your free account if you don’t have one yet. There’s no API key to copy or paste.

For a script, or a tool that can’t sign in, create an API key on your account page in the dashboard and send it as an Authorization: Bearer header instead.

Pick your tool for the exact steps:

  1. Open RunLite in Claude’s directory and click Add. Nothing to install and nothing to paste: it works on every Claude plan, the free one included.
  2. On the RunLite screen, continue with Google or with a code sent to your email. That creates your free account if you don’t have one yet. Then go back to Claude and ask for your website.
Can’t find it? In Claude on the web or desktop, open Customize → Connectors, click +, then Add custom connector, name it RunLite and paste this URL:
https://mcp.runlite.in
Add RunLite on the web or desktop first: it then works in the Claude mobile app the next time you sign in there, even though the app’s own connector search doesn’t list it yet. On a Team or Enterprise plan, an owner adds the connector first, under Organization settings → Connectors.

Tools

Every tool acts as the account you signed in with (or the API key’s account), and new sites count against your plan’s site limit.

get_accountShow the account's plan, its sites and how many more the plan allows, this month's usage (form submissions, deploys, custom domains, bandwidth), and how to move to the next plan. Read-only.
deploy_siteUpload files and make them live. Creates the site on first call; atomic — every file goes live, or none does.
update_siteRe-deploy an existing site. Same operation as deploy_site, with a required site ID.
start_uploadStart a deploy that is sent in several parts, for a site too large for one call.
upload_filesAdd files to an upload, up to 50 per call.
publish_uploadPublish everything an upload holds as one atomic deploy.
read_site_fileRead the current text of one file on the live site, so a later conversation can change it. Read-only.
patch_siteAdd, replace or remove some files of a live site and keep the rest, published as one new version.
create_formCreate a form endpoint and get back ready-to-paste HTML, with spam protection already wired in.
get_formShow one form's fields, where its enquiries go and how many it has had, and give back its HTML. Read-only.
update_formChange a form's fields, name or success message, or pause and resume it. It keeps its address and its enquiries.
configure_notificationsSet where a form's submissions are emailed, or (on paid plans) sent as WhatsApp alerts to an Indian mobile number.
get_submissionsRead recent form submissions.
get_siteShow what a site is serving right now: the live version, each file's size and checksum, recent deployments, and its forms. Read-only.
set_custom_domainStart attaching a domain the customer owns (any paid plan). Returns the DNS record they need to add.
check_custom_domain_statusRe-check a pending custom domain and move it forward until it is live. Safe to call repeatedly.
remove_custom_domainDetach a custom domain; the site is back on its runlitehost.com address immediately.
create_upload_linkMake a photo link (paid plans): a page where someone without a RunLite account sends photos for chosen spots or galleries on a site. What they send waits in the dashboard until it's published.
list_uploadsSee what has come in through a site's photo links (paid plans). A photo can then be deployed as it was processed. Read-only.

How a typical session goes

  1. The first time, you sign in on RunLite’s page with Google or an emailed code.
  2. deploy_site uploads the site’s files and makes them live on a free {subdomain}.runlitehost.com address.
  3. If the site needs a contact form, create_form returns embeddable HTML to include in the files you deploy.
  4. configure_notifications points form submissions at a real inbox. A new address gets a confirmation email first, and enquiries arrive once it’s confirmed. On a paid plan it can also send each enquiry to an Indian (+91) WhatsApp number: the owner opens the returned link on that phone and sends the START message it fills in.
  5. get_submissions reads them back later.

What RunLite won’t publish

  • Anything but static web files. HTML, CSS, JavaScript, JSON, images, fonts, audio, video and PDF are fine; programs, installers and archives are refused. Every deploy needs a root index.html.
  • Login or payment pages on a runlitehost.com address. A page that asks for passwords, card details, one-time codes, PINs or wallet phrases can’t be published on {subdomain}.runlitehost.com. Put it on the site’s own custom domain (any paid plan) instead.
  • Phishing, malware, scams and spam. Deploys are checked automatically. See the Terms, or report a site.

Your own domain

On any paid plan a site can answer at a domain you own, like www.mybakery.com, as well as its runlitehost.com address. It takes two records at your domain provider, which the dashboard or your AI tool gives you one at a time. The step-by-step guide has the clicks for GoDaddy, Hostinger, BigRock, Namecheap, Squarespace and Cloudflare.

Your account

Signing in the first time creates your account on the free Hobby plan. The same sign-in opens the dashboard at app.runlite.in: deployment history, submission inbox, API key management, and billing. You can also sign up there first and connect your AI tool afterwards.

Support

Questions or issues: support@runlite.in. See also the Privacy Policy and Terms of Service.