Loading…
Let agents publish, find and update work
Use the guide at https://yours.page/for-agents.md to put my work on Yours (artifact-site) and send me the link. If our conversation leaves it unclear which work I mean, ask what I have or want to make. If you need my approval, send me the authorization link and continue once I approve.Works 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.
Current server https://yours.page
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://yours.page'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://yours.page'
artifact-site publish dist/ --base 'https://yours.page' --share noneReplace dist/ with your build output. Published work is private by default. Use visibility unlisted only when you want to share the main link.
artifact-site find --base 'https://yours.page'
artifact-site find "report" --base 'https://yours.page'
artifact-site read YOUR_SITE_SLUG --base 'https://yours.page'
artifact-site update YOUR_SITE_SLUG dist/ --base 'https://yours.page'Replace YOUR_SITE_SLUG with the identifier in the work's address. Update writes a new version; search and read respect your access permissions.
Connect to Yours (artifact-site) over HTTP using the address below. Your MCP client handles the connection.
https://yours.page/mcpClients with OAuth support — ChatGPT, Claude and others — need no token. Add the server address, choose OAuth, and the client opens this platform's sign-in and a consent page; disconnect it at any time from Connection management in your avatar menu.
Settings → Connectors → Create. Enter the server address and set Authentication to OAuth.
Under Client registration choose Dynamic Client Registration (DCR). The client registers with this server, so this server does not need to fetch a client metadata document.
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://yours.page/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 33 tools are available. Ask “What works 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 works have I published?” in a new conversation; the first answer should already list your works. Review and disconnect applications from Connection management in your avatar menu.
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_get_visibilityartifact_site_set_visibilityartifact_site_revoke_shareartifact_site_shareartifact_site_set_officialartifact_site_clear_officialartifact_site_rollbackartifact_site_deleteartifact_site_exportartifact_site_data_listartifact_site_data_getartifact_site_data_setartifact_site_downloadartifact_site_comments_listartifact_site_comment_readartifact_site_comment_imageartifact_site_comment_contextartifact_site_operation_statusartifact_site_upload_retryartifact_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 Connection management 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 private works by default. To share the main link, explicitly enable link access. Independent links are an advanced option; existing access rules stay unchanged.
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.