Skip to content
pagesendpagesend
Open navigation
Claude Code guide

Publish from the tools you already use.

Connect Claude Code to a pagesend workspace, transfer finished static files, and publish updates to one stable page.

Connect and check your workspace

Open Agents in pagesend and choose Claude Code. Follow the connection instructions for this deployment, or give Claude Code the Markdown connection guide. If you already use a pagesend plugin connection, keep that connection instead of adding a duplicate server.

Authenticate from Claude Code’s MCP panel. In the pagesend browser window, sign in, select the intended workspace, and review the requested permissions. Return to the client and confirm a read-only call, such as listing your pages, succeeds. Browser consent alone does not prove the client completed the connection.

Publishing normally needs page read and publication access. Managing settings, making a page public, and using runtime data need their own permissions. Keep OAuth tokens in the client’s credential storage.

Prepare finished static output

Ask Claude Code to create an HTML page or the supported static output from your existing project. A bundle includes index.html and relative local assets. Build locally with your usual tools and permissions before uploading. pagesend accepts finished files; it does not run your project’s build or backend.

Keep dependency folders, server files, secrets, and local artifact-binding files outside the output. For interactive saved data, inspect the available collection capabilities before creating the page’s runtime integration. See the runtime guide.

Transfer the actual bytes

Small inline HTML can use the supported publishing tools. Larger HTML, ZIPs, and folders use the package’s local upload helper in an authorized Python 3.12+ macOS or Linux environment. A path on your laptop is not a file the remote MCP server can read.

The helper snapshots the finished files and sends their bytes with a staging-only upload capability. Keep helper state outside uploaded output. If the installed environment cannot use the helper, upload the files in the browser.

Publish deliberately

Ask for a new private page, review validation, and publish only after the files are ready. Preview the result before widening its audience. Public sharing is a separate action requiring explicit approval and the relevant permission.

The local package includes connection, creation, and publishing guidance. Its presence does not imply public marketplace listing or verified compatibility with every client version. Confirm the actual workflow in your installed client.

Update the same page

Keep the returned artifact ID and canonical link. Ask the agent to update that artifact when the files change. It must use the current publication precondition; a conflict should prompt a review, not overwrite someone else’s version.

Disconnect the client from Agents when access is no longer needed. For public discoverability, review search settings separately from publication and audience.