The MCP Connector That Puts Your AI-Built Website Online
The Static.app MCP connector is a hosted Model Context Protocol server at mcp.static.app. Add it to Claude Code, Codex, VS Code or another MCP client with your API key, then ask in plain language. Your AI agent publishes the website, edits single files and hands you a live link in seconds.
Claude CodeClaude DesktopCodexVS CodeDevin DesktopGemini CLI
What Is an MCP Connector?
An MCP connector links an AI app to an outside service using the Model Context Protocol (MCP). Most often it is a remote MCP server you add to your AI tool by URL, which gives the AI a set of actions, called tools, that it can run for you. The Static.app MCP connector gives your AI agent tools to publish, edit, read and download your websites.
MCP is an open standard for connecting AI apps to other tools. A hosted MCP server, a remote MCP server and an MCP connector all describe the same setup here: we run the Static.app MCP server at https://mcp.static.app/sse, and your AI tool connects to it with your Static.app API key. There is no server of your own to host or keep running.
What You Can Ask Your AI Agent
Copy a prompt into Claude Code, Codex or any connected tool. Under each prompt are the Static.app tools your agent will use.
Publish a new website
“Zip the dist folder and publish it on Static.app as a new website called bakery.”
create_uploadcreate_site_from_archive
Change one page
“On my bakery website, change the price on pricing.html from $19 to $29.”
list_sitesread_site_filewrite_site_files
Add a page
“Add a privacy.html page to my bakery website that matches the style of index.html.”
read_site_filewrite_site_files
Ship a new build
“Replace my portfolio website with the new build in the out folder. Keep the same address.”
create_uploadupdate_site_from_archive
See what’s online
“List my Static.app websites with their addresses.”
list_sitesget_site
Clean up files
“Show every file on my landing website and delete the old drafts folder.”
get_site_filesdelete_site_files
Download a copy
“Download my whole bakery website as a ZIP before we start the redesign.”
download_site_archive
Publish from a link
“Publish the ZIP at https://example.com/build.zip as a new website.”
create_site_from_archive
One Conversation, One Live Website
This is a session in Claude Code with the Static.app MCP connector. Every tool name is one your AI agent actually calls.
Claude Code · ~/bakery
› Publish the dist folder as a new website called bakery.1●static-appcreate_upload └ upload_id 9f2c4e… single use, expires in 30 min●Bashcd dist && zip-qr ../site.zip .
●Bashcurl-X PUT --data-binary @../site.zip \
-H"Authorization: Bearer $STATIC_API_KEY" \
<upload_url>●static-appcreate_site_from_archiveupload_id=9f2c4e… name=bakery
└ website createdhttps://bakery.static.domains●Your website is live at https://bakery.static.domains› Change the headline to “Fresh bread every morning”.2●static-appread_site_filepath=index.html
●static-appwrite_site_filesfiles=[{path: index.html, …}]
└ 1 file written●Done. Same address, new headline, live now.› Save a copy of the whole website before we redesign.3●static-appdownload_site_archive └ static.app/storage/zip/…_download.zip●Here’s the ZIP. Anyone with the link can download it.
What just happened
1
Published a new websiteThe agent reserved a one-time upload link, zipped the build and sent it straight from disk, so the file never passed through the chat. Static.app unpacked it and gave the website its own static.domains address.
2
Edited one fileIt read index.html, changed the headline and wrote only that file back. Same address, live right away.
3
Saved a copyIt made a ZIP link of the whole website before the redesign. Anyone with the link can download it.
New websites go live a few seconds after the upload finishes, or 20 seconds or more when you publish from a ZIP link. Website names use lowercase letters and one hyphen. If the name you ask for is taken or not allowed, you get a random address instead.
Connect Your AI Agent in 3 Steps
1
Create an API key
Sign up for the 7-day trial or log in, then open Account > API Keys. Name the key and choose when it expires: 1 day, 1 week, 1 month, 1 year or never.
2
Add the connector
Paste one command or config snippet into your AI tool. It points at https://mcp.static.app/sse and sends your key as a header.
3
Ask for what you want
Start with “List my Static.app websites.” Then ask your agent to publish, edit or download a website. New websites get a live static.domains address in seconds.
Add the MCP Connector to Claude Code, VS Code and More
Every tool connects to the same address, https://mcp.static.app/sse, with your key in an Authorization header. Keep the key in an environment variable called STATIC_API_KEY, so it stays out of your chats and out of config files you share. If your agent asks for the key during an upload, point it to STATIC_API_KEY instead of pasting the key into the chat.
Claude Code
Deploy a website from Claude Code with one command. Set the key in your shell, then add the Static.app MCP server for all your projects:
To share the setup with your team, add a .mcp.json file to your project. The key is read from each person’s environment, so it never lands in the repo:
Claude Desktop connects through mcp-remote, a small bridge that needs Node.js 18 or newer. Open Settings > Developer > Edit Config, add this to claude_desktop_config.json, then restart Claude Desktop:
Claude Desktop can edit, read and download your websites. To publish a new website from files on your computer, use Claude Code or another tool that can run commands, or give it a public ZIP link. The Customize > Connectors screen takes an API key only in Claude’s request headers beta, which is open to a limited set of organizations, so use the config file.
Codex doesn’t connect to SSE servers directly, so it uses mcp-remote, the same small bridge as Claude Desktop. It needs Node.js 18 or newer. Add this to ~/.codex/config.toml, then restart Codex:
In n8n, add an MCP Client Tool node to your AI Agent. Set Endpoint (SSE Endpoint in older versions) to https://mcp.static.app/sse and set Server Transport to Server Sent Events, because the default HTTP Streamable won’t connect. Choose Bearer Auth and save your key as a new credential. n8n can edit, read and download your websites, and publish new ones from a public ZIP link.
Any other MCP client that connects to a remote SSE server works with the same settings, as long as it sends the header with every request:
Check that it works by asking “List my Static.app websites.” If your websites come back, you’re connected. If the tools show up but every action fails, the key is missing or expired: create a new one in Account > API Keys.
Setup steps checked September 2026.
Using claude.ai or ChatGPT?
ChatGPT can’t send an API key to a connector, and claude.ai and the Claude mobile app can do so only in a request headers beta open to a limited set of organizations, so most people can’t use the Static.app MCP connector there yet. For now, publish a Claude artifact by pasting its link into Import from URL on our Claude hosting page. For something ChatGPT built, download it and upload it as a ZIP on our ChatGPT hosting page.
Everything Your AI Agent Can Do on Static.app
The connector gives your agent 12 tools, grouped here by what they do. Every change runs through the Static.app REST API with your key. Your AI tool may also list four form tools, which can’t read form entries yet.
Publish a new website
Send a ZIP from disk or a public ZIP link and get a live address back. Agents that run commands upload the file straight from disk, so it never passes through the chat. Up to 100 MB, within your plan’s storage.
create_uploadcreate_site_from_archive
Replace a whole website
Swap in a new build at the same address. The website is offline while it unpacks, usually for a few seconds, or 20 seconds or more from a ZIP link. For small changes, edit files instead.
update_site_from_archive
Edit single files
Change one page or stylesheet, add up to 200 files at once, or remove old ones. Edits go live right away.
read_site_filewrite_site_filesdelete_site_files
See what you have
List your websites with their addresses, then browse the files in any of them.
list_sitesget_siteget_site_files
Download a copy
Get a ZIP link for a whole website or just the files you pick, so your agent starts from what’s live. Anyone with the link can download it.
download_site_archivedownload_site_files
Delete a website
Removes a website with its files, form entries and domain settings, for good. Keep approval on in your AI tool for this one.
delete_site
Parameters and examples for every tool are in the MCP docs.
Who It’s For
Developers using AI agents
You build in Claude Code, Codex or VS Code and want the result online without setting up git, a build pipeline or a server. Ask your agent to publish, then keep editing in the same chat.
Automation builders
You run workflows in n8n or your own MCP client and want them to update a website: change a page, add files, or publish a ZIP your workflow already hosts.
People who’d rather skip setup
You made something in a chat app and just want it online. Paste a Claude artifact link on our Claude hosting page, or upload a ZIP in the dashboard. No API key needed.
Why Publish AI-Built Websites on Static.app
Static.app is static website hosting built for files, not frameworks. That keeps the path from your AI agent to a live website short.
No git, no build pipeline
Static files are the website. Your agent uploads HTML, CSS, JavaScript and images, and that is what goes live. Building React or Vite? Build locally and publish the output folder.
Big uploads skip the chat
In tools that run commands, like Claude Code, the connector hands your agent a one-time upload link and the ZIP goes straight from disk to Static.app. Only a short upload ID passes through the conversation.
Edit in place, same address
Ask for a new headline or a fixed typo and only that file changes. The address stays the same, and the edit is live right away.
Start from what’s live
Your agent can download the current website as a ZIP, change it and publish it back, so a redesign starts from what is actually online.
A real address right away
Every new website gets its own https://<name>.static.domains address with SSL. On a paid plan, add your own domain with two DNS records.
MCP and REST side by side
Every change the connector makes goes through the Static.app REST API, so your scripts and CI can do the same things with the same key.
You Stay in Control
The connector acts through an API key that you create, name and can revoke. Its tools list the websites in your current workspace, and they can change only websites you own.
The connector’s tools can
Publish new websites, within your plan’s limits
Replace a website or edit its files
List your websites and read their files
Download your websites as ZIP files
Delete files or whole websites, if you let them
The connector’s tools can’t
See or change billing or your plan
Connect domains or change DNS
Delete your account or manage team members
Switch to another workspace
Change websites someone else in your workspace created
Your API key also works with the Static.app REST API, which can do more, such as connecting a domain or switching workspaces. If your AI tool can run commands with your key, treat the key like a password.
Set an expiry. Keys can last 1 day, 1 week, 1 month, 1 year or never. Account > API Keys shows when each key was last used, and deleting or regenerating a key cuts the connector off straight away.
Approve risky actions. Tools like Claude Code and VS Code can ask before each action. Keep that on for delete_site, delete_site_files and update_site_from_archive.
Keep the key out of chat. Put it in STATIC_API_KEY or your tool’s password prompt, never in a message.
Trust one address. The official endpoint is https://mcp.static.app/sse. If your agent reads files or pages you don’t trust, keep delete approvals on so a hidden instruction can’t remove a website.
What It Can’t Do Yet
Connect from ChatGPT, or for most accounts from claude.ai and the Claude mobile app. They need a browser sign-in that the connector doesn’t offer yet.
Publish a new website from Claude Desktop or n8n using files on your computer. Give them a public ZIP link, or use a tool that runs commands.
Connect domains, change DNS or read form entries. Do those in the dashboard, since the form tools your AI tool may list don’t work yet.
Change a teammate’s website in a shared workspace. The tools list the websites in your current workspace, but they read, edit, replace, download and delete only websites you created.
Run server code. Static.app hosts static files, so PHP and Node.js backends won’t run.
If Something Doesn’t Work
No Static.app tools? Restart your AI tool after editing its config. Most read it only at startup. More
401 Unauthorized? Check the key hasn’t expired and the header reads “Bearer sk_…”. More
Connection dropped? The connection closes after about 2 minutes without activity, and most tools reconnect on the next request. More
Upload rejected? Each upload link works once, for 30 minutes, and a ZIP can be up to 100 MB. More
Included on Every Plan
The MCP connector costs nothing extra. Every Static.app account, including the 7-day trial, can create an API key and connect. Plan limits apply to what you create: the trial includes 1 website, and paid plans start at $6 a month ($5 a month billed annually) for 2 websites and a custom domain.
An MCP connector links an AI app to an outside service using the Model Context Protocol (MCP), an open standard for connecting AI apps to other tools. Most often it is a remote MCP server that you add to your AI tool by URL, which gives the AI a set of tools it can run for you. The Static.app MCP connector lets your AI agent publish, edit, read and download your websites.
What’s the difference between an MCP server and an MCP connector?
Usually they are the same thing seen from two sides. The MCP server offers the tools, and AI apps such as Claude call it a connector once you add it. Anthropic also uses “MCP connector” for a Claude API feature that calls remote MCP servers. Static.app runs its MCP server at https://mcp.static.app/sse, so you don’t host anything yourself.
Are Claude connectors the same as MCP servers?
Close. In Claude, connectors are how you plug in outside apps, and a custom connector is a remote MCP server added by URL. Claude Code, and Claude Desktop through its config file, can connect to the Static.app MCP server today. The Connectors screen in claude.ai and Claude Desktop (Customize > Connectors) can send an API key only in a request headers beta open to a limited set of organizations, so for most accounts the Static.app MCP connector can’t be added there yet.
Which AI tools work with the Static.app MCP connector?
Claude Code, Codex and Claude Desktop (both through the mcp-remote bridge), VS Code with GitHub Copilot agent mode, Devin Desktop (formerly Windsurf), Gemini CLI and n8n. Claude Desktop and n8n can edit, read and download websites, and publish new ones from a public ZIP link. Any MCP client that connects to a remote SSE server and sends an Authorization header with every request works too. ChatGPT can’t connect yet, and claude.ai and the Claude mobile app can’t for most accounts.
Can I add Static.app as a custom connector in claude.ai or ChatGPT?
Not yet for most accounts. ChatGPT developer mode (apps) has no way to send an API key, and claude.ai custom connectors can send one only in a request headers beta open to a limited set of organizations. The Static.app MCP connector needs a key. Claude Desktop users can connect today with the config file in the setup section.
Can I publish a Claude artifact or a page ChatGPT made?
Yes, and you don’t need the connector for it. Paste a public Claude artifact link into Import from URL on our Claude hosting page, or follow our guide on how to host a Claude artifact. For a page ChatGPT made, download the files and upload them as a ZIP on our ChatGPT hosting page.
Do I need to host an MCP server?
No. There’s no MCP hosting to set up: the server runs at https://mcp.static.app/sse and serves every Static.app account, with each person connecting through their own API key. Claude Desktop and Codex run a small local bridge, mcp-remote, which needs Node.js 18 or newer. The other tools connect to the URL directly.
Is the MCP connector included in my plan, and can I try it first?
Yes. Every Static.app account can create an API key and use the connector, including during the 7-day trial. Plan limits apply to what you create: the trial includes 1 website, and paid plans start at $6 a month, or $5 a month billed annually.
Do I need to know how to code?
No, but setup means pasting one command or config snippet into an AI tool such as Claude Code or VS Code. After that you ask in plain language. If you’d rather skip setup, upload a ZIP in the dashboard or import a Claude artifact link.
Can it publish React, Vite or Next.js projects?
Yes, as static files. Ask your agent to build the project, for example with npm run build, and publish the output folder, such as dist. For Next.js, turn on static export (output: “export” in next.config) first, which writes an out folder. Static.app serves static files, so API routes, server rendering, PHP and Node.js backends won’t run.
Will my website keep the same address when my AI updates it, and can I use my own domain?
Yes. Replacing a website or editing single files keeps the same address, and file edits are live right away. Every new website gets its own static.domains address with SSL. To use your own domain, connect it in the dashboard on a paid plan by adding two DNS records. The connector itself doesn’t change domains or DNS.
Is it safe to let an AI agent manage my websites?
The connector’s tools can only publish, edit, download and delete websites you own. They can’t touch billing, connect domains or switch workspaces. Your key also opens the Static.app REST API, so give it an expiry, keep approvals on for delete actions, and delete it in Account > API Keys to cut access.
Connect Once. Ask for the Rest.
Create a key, paste one snippet, and let your AI agent publish your next website.
Essential cookies keep Static.app working. Optional cookies help us understand usage and attribute referrals.
You can choose what to allow.
Cookie settings
Choose what Static.app can use
We keep essential cookies on for security, sessions, uploads, and remembering this choice. Optional categories stay off unless you enable them.
Essential and securityLaravel session and persistent login, CSRF protection, consent choice, upload/session features, anti-abuse checks (Cloudflare Turnstile and Google reCAPTCHA where needed), payment and fraud prevention through Stripe, and our HelpScout support chat. Also includes cookieless tools that set no cookies and store no personal identifiers: Plausible analytics, the Pulsetic status badge and performance (RUM) monitoring, and Google Analytics in cookieless mode.
Always on
What is not optional:
account sessions, CSRF protection, payment/security workflows, uploaded file handling, and abuse prevention. These are needed to provide the service safely.