STEP 01
Connect it once
Copy one line into Claude, Cursor, or Codex. Nothing to download or install.
MCP server
Ask your AIto build it.Watch it go live.
Connect Nanopage to Claude, Cursor, or Codex, then just say “put this online”. Your AI builds the website. Nanopage gives it a real web address and keeps it running.
One lineto set upNo keys to copy around
“Build a one-page site for this project using the notes and photos in this folder, then put it online as Field Notes.”
A minute later you have a working web address you can send to anyone.
One lineSetting it up
NoneKeys to manage
SecondsTime to live
What it isYour AI can build a website.
Your AI can build a website.
Now it can publish one.
Tools like Claude, Cursor, and Codex are good at making web pages. Getting those pages onto the internet has always been the awkward part. Connecting Nanopage removes that step.
MCP is simply the standard way AI tools plug into other services. You do not need to know anything about it beyond copying one line.
Connect it in about a minutePick your tool,
Pick your tool,
copy the line, paste it in.
One command. The first time you use it, Claude opens your browser so you can sign in and say yes.
Run this in your terminal
claude mcp add --transport http nanopage https://api.nanopage.site/mcpRestart your AI tool afterwards and you should see nanopage in its list of connections. Setting this up for a build server instead of your own machine? The setup page has that covered.
STEP 02
Say yes
Your AI tool opens Nanopage in your browser. You sign in and approve — no keys or passwords to copy around.
STEP 03
Ask it to publish
Say “put this online”. You get a real web address back, live, before the conversation ends.
What it can doAsk in plain English.
Ask in plain English.
It picks the right one.
Put a new site online
Takes the pages your AI wrote and gives them a live web address.
publish_website
Update a site you already have
Changes go live straight away. The old version is kept, so nothing is lost.
publish_version
Add photos, videos, and files
Images and downloads get uploaded properly instead of being squeezed into the chat.
create_upload
Check a web address is free
Before claiming a name, it checks whether it is taken and suggests one that works.
suggest_slug
See what you already have
Your AI can look up the sites in your account and what is on them.
list_websites · get_website
Look back at earlier versions
Every publish is kept, so you can see the history and go back if you need to.
list_versions · get_job_status
The result usually works first time.
Before it builds anything, your AI can pull up a short guide from Nanopage explaining what a site here can and cannot include. That is why the result usually works first time instead of being rejected on the way out.
Who does whatYour AI does the building.
Your AI does the building.
Nanopage keeps it alive.
Writes what goes live.
- Writes the pages, the words, and the design
- Uses whatever is already in your project — notes, images, files
- Makes changes when you ask for them
Nothing is rewritten behind your back. What your AI shows you is what goes live.
Handles the boring parts.
- Checks the site works before anyone sees it
- Gives it a web address and keeps it online
- Saves every version so you can go back
- Handles the hosting, security, and speed
What kind of sites work hereSelf-contained websites.
Self-contained websites.
Fast, simple, hard to break.
Photos, videos, and downloads are all fine — up to 50 MB per file and 1 GB per site.
A great fit
- Landing pages and one-pagers
- Portfolios, résumés, and project write-ups
- Documentation, guides, and read-me sites
- Event, launch, and campaign pages
Look elsewhere for
- Sites needing logins or user accounts
- Shops with checkout and payments
- Anything that needs its own database
It can publish. That is all.
Connecting your AI lets it put sites online, update them, and look at the ones you already have. It cannot reach your billing, your payment details, your domains, or your account settings — and you can disconnect it whenever you like.
The technical details.
If you want the endpoint, the tool reference, permission scopes, or the plain HTTP API underneath it all, that is what the developer pages are for.
Questions, answeredThe short answers
The short answers
before you connect.
Do I need to be a developer?+
You need one of the AI coding tools — Claude Code, Claude Desktop, Cursor, or Codex — and about a minute to connect it. After that you just talk to your AI in plain English and ask it to publish. There is no code for you to write.
Is there a password or key to set up?+
No. Your AI tool opens Nanopage in your browser, you sign in as normal, and you approve the connection once. Nothing to copy, paste, or keep somewhere safe.
What can it actually reach in my account?+
Only publishing. It can put sites online, update them, and look at what you already have. It can never reach your billing, your payment details, your domains, or your account settings.
Does Nanopage write the site as well?+
No — and that is the point. Your AI writes every page itself, so what you see in the conversation is exactly what goes live. Nanopage takes care of the hosting. If you would rather Nanopage did the writing, the normal Nanopage builder does exactly that.
Can it handle photos and videos?+
Yes. Your AI uploads them properly rather than cramming them into the chat. Files can be up to 50 MB each, and a site can hold up to 1 GB in total.
What if I want to change something later?+
Just ask. Each time your AI publishes, the update goes live immediately and the previous version is kept, so you can always look back or go back.
Stop stopping to deploy.
Read the walkthrough, or connect your AI and ask it to publish something.