Your AI just wrote a web page. Give it a real link in seconds.
Take the HTML file from Claude, ChatGPT, v0, Lovable or Cursor, drop it on Li2 and get a link that opens on any device. Or connect MCP and let Claude publish and update it by itself. Passwords, access control, no hosting. PDFs, slides and video work too.
Build me a landing page for my course as a single HTML file
What do you want to put online?
Pick the kind of content, drop the file in, get a link. No domain, no server, no command line.
Drop your document here
PDF · PowerPoint
or click to choose a file — up to 10 MB
Quotes, capability decks, presentations. Recipients read it from the link instead of downloading a file.
Free to start · no card needed · done in 30 seconds
What did you just build with AI that someone else needs to open?
Artifact is for the pages AI makes in minutes that then get stuck in a preview pane. Drop them on Li2 and they become real addresses you can send.
Claude artifacts
The Share button on claude.ai gives you a link inside Claude's viewer, open to anyone, with no password option.
Download the artifact as HTML and drop it on Li2, or connect MCP and let Claude publish it. You get your own slug and control over who views it.
Pages written by ChatGPT or Gemini
ChatGPT writes an HTML page in seconds, but getting it in front of a client means finding somewhere to host it.
Copy the code into an .html file and drop it on Li2. No GitHub account, no deploy step.
Exports from v0, Lovable, Bolt
The export is a whole project; sharing a static version means running a build and finding hosting.
Ask the tool for a single self-contained index.html and publish it on Li2. Viewers just click the link.
Prototypes for client review
Email an HTML file and it breaks on the client's phone or triggers a security warning on their laptop.
One link with a password, sent to the client. Apply their feedback, replace the file, and the same link shows the new version.
AI-built dashboards and reports
Claude Code just built a dashboard from internal numbers, but it cannot be public for the whole world.
Publish in private mode so only organisation members can open it. Or use Google sign-in to know who viewed it.
PDFs, slides and video too
PDF reports, slide decks and demo videos still go out as heavy attachments you cannot fix after sending.
Artifact also accepts PDF, PowerPoint and video up to 10 MB. Same publish flow, same access modes, same fixed link.
Three steps, under a minute
No hosting, no domain, no command line. If you have the file from your AI, you have the link.
Get the HTML file from your AI
Ask Claude, ChatGPT or v0 for a single self-contained HTML file and download it. Or skip this step: connect MCP and let Claude publish directly.
Drop it on Li2, pick a slug
Drag in the file, give it a name and a slug like li2.ai/python-course. Choose public or password right here.
Publish and send the link
A safety check runs for a few seconds, then you get the link. The page runs in an isolated environment and opens on any device.
Everything you need, without asking anyone
Edit the content, set a password, capture viewer emails, generate a QR code — all from the dashboard, no developer required.
Make edits any time
Upload a new file and the path stays the same. Anyone holding the link lands in the right place and sees the latest version.
Capture viewer emails
Require a Google sign-in before viewing. Emails and open times land straight in your Customers list.
Password protect
Only people with the password get in. Remembered for a week, locked for ten minutes after three wrong tries.
Generate QR codes
Every page ships with a QR code. Change what is behind it without reprinting the code.
Keep it inside your org
Only members of your organisation can open it. Built for internal dashboards and documents.
Let agents publish over MCP
Claude calls publish_artifact and update_artifact. No uploading or downloading on your side, just the link.
HTTPS and file scanning included
Every page gets a certificate, runs in an isolated sandbox and is scanned for safety before it goes live.
Take it down with a note
People opening the old link see a removal notice with how to reach you, not a confusing 404.
Let Claude publish and update on its own
Connect Li2's MCP server to Claude Desktop, Claude Code or whichever agent you use. The agent calls publish_artifact to put the page online and update_artifact when you ask for changes. You just get the link, with nothing to upload or download.
- 1
Connect Li2's MCP server
Add Li2 to the MCP servers in Claude Desktop, Claude Code or whichever agent you use, authenticated with a scoped API key.
- 2
The agent calls publish_artifact
It passes the HTML content, a name and a slug. The result is a link that opens right away.
- 3
To fix something, it calls update_artifact
The agent replaces the content at the same slug. The link stays the same and everyone who has it sees the new version.
How is this different from the Share button on claude.ai?
- A claude.ai share link is open to anyone; you cannot set a password or restrict who views it.
- The page stays inside claude.ai's viewer, with no address of its own to put on a CV or send to a client.
- On Li2 you choose the access mode, pick a memorable slug and replace the content without resending the link.
Beyond the two artifact tools, Li2's MCP server also offers tools to create short links and read analytics, so an agent can publish and report in one go.
Iterate with AI as many times as you like, the link stays one
Working with AI means constant revisions. Each round you replace the file, or let the agent call update_artifact. The link you sent to the client, your boss or the team always opens the latest version, and nobody gets a new link.
Replace the artifact's file. The short link stays the same.
Finished landing-v1.html, published at li2.ai/python-course
Sent for review: li2.ai/python-course. Client wants new colours and a pricing section
The client reopens the same link and sees the revised page
- You can even change the file type: swap the HTML page for a PDF and visitors see the PDF viewer instead of the web page.
- The old file is replaced for good. If you still need it, the app reminds you to download the current version first.
- Storage only counts the difference between the new and old file.
Choose who can view, change it anytime
Four access modes for the same link. Switching takes effect immediately, with no new link and nothing to resend.
Public
Anyone with the link
The default for landing pages, portfolios and public demos. Click and it opens, no questions asked.
Private
Members of your organisation
For AI-built dashboards and internal reports. Viewers sign in to Li2 and must belong to your organisation; outsiders only see a notice page.
Password
Anyone who knows the password
For prototypes sent to clients for review. Enter it once and view for a week. Three wrong attempts lock it for 10 minutes.
Google sign-in
Anyone with a Google account
Each viewer's email and viewing time is saved under Customers. Good for quotes, company profiles and event handouts.
Changing the access mode never changes the link. Same for the password: the link stays, viewers just enter the new password.
Take it down without a dead link
The prototype is approved, the campaign ends, or you just want to pause sharing. Deleting an artifact leaves no 404 wherever you sent the link.
When you delete, the file is removed from storage but the link keeps working. Visitors see a notice that the content was taken down, with a hint to contact the publisher for the latest version, instead of an error page that makes the link look broken.
- The slug stays reserved; nobody else can register it.
- To reuse it, create a new artifact and publish, or point the link to a new destination.
- Visits to the notice page are still recorded, so you know whether the old link is still being used.
This content has been taken down
The publisher removed the content at this address.
The link you opened is not broken.
You reached the right address. Contact whoever sent you the link for the latest version.
A short link and QR code come included
Every artifact comes with a Li2 short link and a dynamic QR code, handy when you need to put it on a slide, a business card or a printout.
Limits and plans
Every plan includes all the Artifact features above, MCP included. Plans differ in quantity and storage.
Artifact FAQ
What people working with Claude, ChatGPT, v0 or Lovable ask before publishing their first page.
Yes. Upload the HTML file like any other, or connect Li2's MCP server so Claude can call publish_artifact directly. The page runs in an isolated environment without external scripts, so it needs to be a single self-contained HTML file.
Ask the AI for a single index.html with CSS and JavaScript inlined. Claude, ChatGPT and v0 all do this when asked clearly. Li2 does not accept multi-page folders or zip files yet.
Create a scoped API key in Li2 and add Li2's MCP server to Claude Desktop, Claude Code or your agent. Then just tell Claude: publish this page to Li2 at slug abc. Claude calls publish_artifact and returns the link; for edits it calls update_artifact.
A claude.ai share link lives inside Claude's viewer, is open to anyone and cannot be password-protected. On Li2 the page has its own slug that you choose, four access modes, content you can replace without changing the link, and a notice page instead of a dead link if you take it down.
PDF, PowerPoint and video, up to 10 MB each, with the same publish flow and access modes as HTML pages. PowerPoint is shown through Microsoft's viewer, PDFs open in the browser's viewer and videos get their own player. Word, Excel and markdown are not supported yet.
No. Click Update content and drop in the new file, or let Claude call update_artifact. The link stays the same and everyone who has it opens the new version. Only the slug is fixed after publishing; the display name and access mode can change at any time.
Your AI did the hard part. Let Li2 put it online.
Create a free account, publish your first HTML page and send the link within a minute. Connect MCP when you want Claude to do it for you. Upgrade for more artifacts without changing a single link.