YeetIt

Official4 toolsLive

by snappyio

Instant web publishing for AI agents. POST HTML, get a live URL. No account needed.

io.github.snappyio/yeetit — Model Context Protocol (MCP) Server

The io.github.snappyio/yeetit MCP server provides instant web publishing for AI agents. It accepts an HTML payload via HTTP POST and returns a live URL for the published content. The server requires no account and is described as enabling agent workflows that produce and share web pages.

🛠️ Key Features

Instant web publishing for AI agents
POST HTML to publish content
Returns a live URL
No account required

🚀 Use Cases

Publishing HTML generated by AI agents
Sharing a live URL after HTML is produced
Agent-driven web page creation and distribution

⚡ Developer Benefits

Simple request/response flow: POST HTML → live URL
Integrates with systems that already generate HTML
Avoids account setup

⚠️ Limitations

Limited details provided beyond HTML POST and live URL output
Tool capabilities are not specified beyond a reported toolCount of 4

Captured live from the server via tools/list.

publish_website

Publish HTML content to a live URL instantly. No account or API key required. Returns a public URL that anyone can visit. Sites expire after 24 hours unless the owner claims them. Use this when a user asks you to build, create, or deploy a website, landing page, invitation, portfolio, report, or any HTML content they want to share as a link. Supports bundled assets (CSS, JS, images) and multi-page sites (include additional .html files in assets, accessible at /{slug}/{pagename}). IMPORTANT: After publishing, always share the live URL and the claim URL with the user. The claim URL lets them take permanent ownership of the site. Store the edit_key from the response silently — do not show it to the user — you will need it if they ask you to make changes to the site later. If you lose the edit_key, ask the user to claim the site first (via the claim URL in the page footer), then provide you with their API key from the dashboard — you can use that instead.

Parameters3

html	string	required	Complete HTML document to publish. Must be a valid, self-contained page. Inline CSS and JS are supported. External resources (images, fonts, scripts) must use absolute URLs OR be included in the assets field with relative references (e.g. href="./style.css" or src="./logo.png"). Maximum total size including assets: 5.0MB (free tier) or 10 MB (Pro/Business).
title	string	optional	Human-readable title for the published page. Used in social sharing previews and the claim page. Optional.
assets	object	optional	Optional map of filename to content for bundled assets. Keys are filenames (e.g. "style.css", "logo.png", "app.js"). Values are either plain text strings (for CSS, JS, SVG, HTML) or data URIs for binary files (e.g. "data:image/png;base64,iVBOR..."). Reference these in your HTML with relative paths like ./style.css or ./logo.png. For multi-page sites, include additional .html files (e.g. "about.html") which become accessible at /{slug}/about. Limits: 10 assets (free) or 50 assets (Pro/Business), 5 MB max per individual asset, but total site size (HTML + all assets) must be under 5.0MB (free) or 10 MB (Pro/Business).

Raw schema

{
  "type": "object",
  "properties": {
    "html": {
      "type": "string",
      "description": "Complete HTML document to publish. Must be a valid, self-contained page. Inline CSS and JS are supported. External resources (images, fonts, scripts) must use absolute URLs OR be included in the assets field with relative references (e.g. href=\"./style.css\" or src=\"./logo.png\"). Maximum total size including assets: 5.0MB (free tier) or 10 MB (Pro/Business)."
    },
    "title": {
      "type": "string",
      "description": "Human-readable title for the published page. Used in social sharing previews and the claim page. Optional."
    },
    "assets": {
      "type": "object",
      "description": "Optional map of filename to content for bundled assets. Keys are filenames (e.g. \"style.css\", \"logo.png\", \"app.js\"). Values are either plain text strings (for CSS, JS, SVG, HTML) or data URIs for binary files (e.g. \"data:image/png;base64,iVBOR...\"). Reference these in your HTML with relative paths like ./style.css or ./logo.png. For multi-page sites, include additional .html files (e.g. \"about.html\") which become accessible at /{slug}/about. Limits: 10 assets (free) or 50 assets (Pro/Business), 5 MB max per individual asset, but total site size (HTML + all assets) must be under 5.0MB (free) or 10 MB (Pro/Business).",
      "additionalProperties": {
        "type": "string"
      }
    }
  },
  "required": [
    "html"
  ]
}

update_website

Update an existing published website with new HTML content. Requires authentication via edit_key (from the original publish response) or api_key (from the user's dashboard after claiming the site). The html field replaces the entire page — this is a full replacement, not a patch. You can also update assets. Use this when a user asks you to modify, edit, or change a site you previously published. IMPORTANT: You must provide either edit_key or api_key for authentication.

Parameters6

slug	string	required	The slug of the site to update (e.g. "hello-world-k3m").
html	string	required	Complete HTML document to replace the existing page with. Must be a valid, self-contained page. This replaces the entire page content.
title	string	optional	Optional new title for the page.
assets	object	optional	Optional map of filename to content. If provided, replaces ALL existing assets. Omit to keep existing assets unchanged.
edit_key	string	optional	The edit key returned when the site was originally published (e.g. "ek_9c4d2e7f..."). Use this if you still have it from the publish response.
api_key	string	optional	The user's API key from their dashboard (e.g. "yt_abc123..."). Use this if the user has claimed the site and provided their API key.

Raw schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "The slug of the site to update (e.g. \"hello-world-k3m\")."
    },
    "html": {
      "type": "string",
      "description": "Complete HTML document to replace the existing page with. Must be a valid, self-contained page. This replaces the entire page content."
    },
    "title": {
      "type": "string",
      "description": "Optional new title for the page."
    },
    "assets": {
      "type": "object",
      "description": "Optional map of filename to content. If provided, replaces ALL existing assets. Omit to keep existing assets unchanged.",
      "additionalProperties": {
        "type": "string"
      }
    },
    "edit_key": {
      "type": "string",
      "description": "The edit key returned when the site was originally published (e.g. \"ek_9c4d2e7f...\"). Use this if you still have it from the publish response."
    },
    "api_key": {
      "type": "string",
      "description": "The user's API key from their dashboard (e.g. \"yt_abc123...\"). Use this if the user has claimed the site and provided their API key."
    }
  },
  "required": [
    "slug",
    "html"
  ]
}

delete_website

Permanently delete a published website. The site will be immediately inaccessible. Requires authentication via edit_key or api_key, and requires confirm: true as a safety mechanism to prevent accidental deletion. Use this when a user explicitly asks you to remove or delete a site. IMPORTANT: Always confirm with the user before calling this tool — deletion cannot be undone.

Parameters4

slug	string	required	The slug of the site to delete (e.g. "hello-world-k3m").
confirm	boolean	required	Must be set to true to confirm deletion. This is a safety mechanism — the tool will refuse to delete without explicit confirmation.
edit_key	string	optional	The edit key for this site (e.g. "ek_9c4d2e7f...").
api_key	string	optional	The user's API key (e.g. "yt_abc123...").

Raw schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "The slug of the site to delete (e.g. \"hello-world-k3m\")."
    },
    "confirm": {
      "type": "boolean",
      "description": "Must be set to true to confirm deletion. This is a safety mechanism — the tool will refuse to delete without explicit confirmation."
    },
    "edit_key": {
      "type": "string",
      "description": "The edit key for this site (e.g. \"ek_9c4d2e7f...\")."
    },
    "api_key": {
      "type": "string",
      "description": "The user's API key (e.g. \"yt_abc123...\")."
    }
  },
  "required": [
    "slug",
    "confirm"
  ]
}

get_website_status

Get information about a published website including its title, view count, size, expiry date, and whether it has been claimed. No authentication required — this is public information. Use this to check if a site is still live, see how many views it has gotten, or check when it expires.

Parameters1

slug

string

required

The slug of the site to check (e.g. "hello-world-k3m").

Raw schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "The slug of the site to check (e.g. \"hello-world-k3m\")."
    }
  },
  "required": [
    "slug"
  ]
}

Install

Tools (4)

publish_websiteupdate_websitedelete_websiteget_website_status

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://yeetit.site/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "yeetit": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://yeetit.site/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

io.github.snappyio/yeetit — Model Context Protocol (MCP) Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

publish_website

update_website

delete_website

get_website_status

Install

Remote endpoint

Related servers