Upfling.host

Upfling provides a zero-configuration environment for hosting static websites.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • List Sites: List all sites owned by the authenticated user. Returns id, subdomain, live URL, status, and basic metadata for each site.
  • Get Site: Get details of a single site, including its live URL, storage size, and current status.
  • Read Site File: Read the content of a single file on a site. Use mode: 'inline' to get the file content directly (text as UTF-8, binary as base64). Use mode: 'link' to get a short-lived authenticated

What data it sees

Do you need an account

No: the server works without sign-in

Upfling provides a zero-configuration environment for hosting static websites. You can upload individual HTML, CSS, and JS files or drag an entire folder to receive a live website with SSL on a shareable URL in seconds. It eliminates the need for complex setup or server configuration, focusing on rapid deployment for static web projects.

You can also upload documents like PDFs and add password protection.

All of this can be done using the API or MCPs from AI chat platforms.

How to connect

How to connect Upfling.host to Claude

The server address to paste into Claude settings:

https://upfling.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Upfling.host to ChatGPT

The server address to paste into ChatGPT settings:

https://upfling.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Upfling.host to Cursor

The server address to paste into Cursor settings:

https://upfling.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (15)

Raw names from tools/list. Only developers need these.

list_sitesList all sites owned by the authenticated user. Returns id, subdomain, live URL, status, and basic metadata for each site.
get_siteGet details of a single site, including its live URL, storage size, and current status.
read_site_fileRead the content of a single file on a site. Use mode: 'inline' to get the file content directly (text as UTF-8, binary as base64). Use mode: 'link' to get a short-lived authenticated download URL instead — useful for large files or when passing the URL to another tool. Use mode: 'auto' (default) to inline files under 100 KB and return a link for larger ones. Inline reads are capped at 1 MB.
list_site_filesList files on a site. Returns path, size in bytes, content type, and live URL for each file.
get_account_infoReturns the authenticated user's plan, storage used, site count, and plan limits. Useful for checking whether a new site can be created or what storage is remaining.
searchSearch the authenticated user's own sites by subdomain, custom domain, title, description, and file path (case-insensitive substring; not file contents). Returns up to 20 results as {id, title, url}: ids are 'site:<site_id>' or 'file:<site_id>:<path>', and url is the live address. Pass an empty query to list the user's sites. Use fetch with a returned id to read it.
fetchFetch one search result by id. 'site:<site_id>' returns a readable summary of the site (title, live URL, status, storage, dates, first 100 files). 'file:<site_id>:<path>' returns the file's content as UTF-8 text when it is a text type of at most 1 MB, otherwise a short note pointing at its live URL. Returns {id, title, text, url, metadata}.
create_siteCreate a new site with inline text files (HTML, CSS, JS, SVG, JSON, etc.). For large or binary files, use request_upload without a site_id instead — it creates the pending site and upload batch in one operation. Inline limit: 200 files, 1 MB per file.
write_site_filesAdd or overwrite specific files on an existing site without touching other files. Use this to update an existing page, add a new asset, or fix a typo. Limit: 200 files per call, 1 MB per file.
replace_site_filesReplace ALL files on a site with a new set. Any file not included in this call is deleted. Use when rebuilding a site from scratch. Limit: 200 files per call, 1 MB per file.
request_uploadReserve presigned PUT URLs for uploading one or more large or binary files directly to storage — bypassing the 1 MB inline limit. Omit site_id to create a new pending site atomically (supply subdomain/title for the new site). Provide site_id to add or replace files on an existing site. The caller must PUT each file to its returned upload_url, then call confirm_upload once with the batch upload_id.
confirm_uploadFinalize a batch of uploads after the caller has PUT all file bytes to the presigned URLs returned by request_upload. The site goes live (or is updated) only after this call succeeds. All files in the batch are published atomically.
update_siteUpdate a site's metadata: title, subdomain (changes the live URL), description, password protection, or homepage file. Omit any field to leave it unchanged.
delete_site_filesDelete a specific file from a site. The site stays live; only that one file is removed.
delete_siteDelete a site. By default the site is moved to trash and can be recovered. Pass permanent: true to delete immediately and permanently — this cannot be undone.