Loading…
Choose one way to connect the tools you already use.
Publish this project's output (a web page or a PDF/Office document) to artifact-site. Publishing guide: https://artifacts.klemet.net/for-agents.mdWorks with Claude Code, Cursor, Codex and other assistants that can read a URL.
Send it to the agent you are working in.
If it asks to sign in, approve the terminal session you started yourself.
Open the published work and choose who can access it.
Ask the agent to update a site, search previous work or read its text. It follows the server's publishing and access policies.
Current server https://artifacts.klemet.net
The CLI provides all operations from your terminal. MCP connects remotely without installing it.
Requires Node 24+ and npm on the machine running your CLI or agent.
npm install -g @artifact-site/cliIf artifact-site is not found, check npm's global bin directory is on PATH, then restart your terminal or agent client. If npm reports EACCES, use a user-writable npm prefix; see the CLI README for commands.
artifact-site login --base 'https://artifacts.klemet.net'Open the verification page, sign in and approve the session you started. The CLI saves this personal credential on this machine.
artifact-site whoami --base 'https://artifacts.klemet.net'
artifact-site publish dist/ --base 'https://artifacts.klemet.net' --share noneReplace dist/ with your build output. A successful publish returns the site address. This example creates no share link; omitting --share defaults to a public share.
artifact-site find --base 'https://artifacts.klemet.net'
artifact-site find "report" --base 'https://artifacts.klemet.net'
artifact-site read YOUR_SITE_SLUG --base 'https://artifacts.klemet.net'
artifact-site update YOUR_SITE_SLUG dist/ --base 'https://artifacts.klemet.net'Replace YOUR_SITE_SLUG with the identifier in the site's address. Update writes a new version; search and read respect your access permissions.
Connect directly to this server over HTTP. No Node.js, CLI installation or local MCP process is needed.
https://artifacts.klemet.net/mcpClients with OAuth support — ChatGPT, Claude and others — need no token. Add the server address, choose OAuth, and the client opens this site's sign-in and a consent page; disconnect it at any time from My sites.
Settings → Connectors → Create. Enter the server address and set Authentication to OAuth.
Under Client registration choose Dynamic Client Registration: ChatGPT connects to this server, so it works from any network. Client ID Metadata Document also works, but only if this server can reach chatgpt.com — if the consent page says the client metadata document could not be fetched, switch to Dynamic Client Registration.
Leave the default scopes empty: this server asks for artifacts:read and artifacts:write itself. Create, then approve the connection in the window ChatGPT opens.
Add a custom connector or remote MCP server with the address alone, without a token or header. When the client asks you to sign in, approve the connection in the browser window it opens.
{
"mcpServers": {
"artifact-site": {
"url": "https://artifacts.klemet.net/mcp"
}
}
}For clients configured with a JSON file. This entry holds no credential; the client starts the sign-in itself. ChatGPT needs no configuration file.
Reload the client and check that 26 tools are available. Ask “What artifacts have I published?” without naming MCP. Then publish a test file, read it back and delete it. Use artifact_site_connection to diagnose identity or limits.
In ChatGPT, ask “What artifacts have I published?” in a new conversation; the first answer should already list your sites. Connected applications can be reviewed and disconnected in My sites.
Publish and update · Search and read · List and share
Your MCP client discovers each tool's parameter schema automatically. Export, rollback and delete are also available; confirm destructive actions before use.
artifact_site_connectionartifact_site_publishartifact_site_updateartifact_site_editartifact_site_findartifact_site_foldersartifact_site_moveartifact_site_get_siteartifact_site_readartifact_site_forkartifact_site_shareartifact_site_set_officialartifact_site_clear_officialartifact_site_rollbackartifact_site_deleteartifact_site_exportartifact_site_comments_listartifact_site_comment_readartifact_site_comment_imageartifact_site_comment_resultartifact_site_comment_contextartifact_site_operation_statusartifact_site_upload_statusartifact_site_upload_startartifact_site_upload_writeartifact_site_upload_cancelThe artifact-site://skill resource provides the publishing contract and runtime limits. Full HTTP API details remain in the publishing guide below.
CLI and remote MCP use the same Bearer credentials and account permissions. Configure each client separately. Operator tokens have broad privileges; remote MCP requires authentication for every request.
In CLI, an environment token overrides a saved token. Check the server address and stale ARTIFACT_SITE_TOKEN when authentication fails. CLI logout removes local credentials; revoke a personal token in My sites to stop its use by every client.
A cloud agent cannot reach localhost on your computer. Use a server address reachable from the agent. The browser cannot detect whether the CLI is installed or connected on another machine.
CLI and MCP create public shares by default when publishing. Use --share none in the CLI or share: false in MCP to keep new work unshared; existing site visibility and sharing rules still apply.
HTML, folders, ZIP, PDF and Office documents. Sizes, formats and what a hosted page may do at runtime are set out in the full guide below.