Quickstart

This walkthrough uses Claude Code to go from setup to creating, reviewing, publishing, and sharing your first page. For other MCP clients and TrayPage agent skill setup, see MCP / Skill. If MCP is unavailable, or you want to use TrayPage from scripts, the CLI can run the same publish and review workflow.

1. Sign in

Sign in at https://tray.page. After your first sign-in, TrayPage creates a Personal workspace and default project for you automatically, so you can start publishing right away. During the beta, each created workspace receives a one-month Pro trial automatically. For team use, you can create a team workspace later and move pages into it.

2. Add the MCP server

Run this in your terminal:

claude mcp add --transport http --scope user traypage https://tray.page/api/mcp

Inside Claude Code, run /mcp, select traypage, and authenticate. A browser opens: sign in, confirm the workspace, projects, and default project you're granting, and you're connected. No manual token copying needed.

If each repository should use a different TrayPage workspace or project, you want repository-scoped setup, or you want your agent to run the TrayPage publish, review, and revision loop consistently, see MCP / Skill.

3. Create a draft page

Ask Claude Code to create a deliverable and send it to TrayPage. Both HTML and Markdown work:

Create a sales analysis report in HTML and send it to TrayPage

Claude Code sends the page to TrayPage and returns a review URL and a share URL. The first version starts as a draft. Without an explicit target, the page goes to the default project you chose when connecting. To create it elsewhere, name the project: "create it in the reports project".

4. Review and check visibility

Open the review URL to see the page preview with a comment panel. Team members can select text and comment on it.

Sharing access starts from the project's default and can be changed per page. If you want to share outside the project, choose an option such as Anyone with the link in the sharing dialog. Sharing access controls who can open the share URL; it does not make a draft version appear on that URL.

5. Publish the version and share it

When the content is ready, ask Claude Code to publish the version:

Publish v1 of this page so it is visible from the share link

Claude Code makes the reviewed version live. Only the live version is shown from the share URL. The share URL itself does not change; the content behind it switches to the live version.

Open the share URL and confirm the intended audience can see the page body. If the page is not set to Anyone with the link, people outside the selected sharing access still cannot view it even if they have the URL.

6. Iterate on comments

Once comments come in, ask Claude Code to revise:

Apply the TrayPage comments and create a revised version

Claude Code turns open comments into revision instructions, then creates a new draft version. Version history is kept automatically. To show the revised version from the share URL, review it and then publish that version.

In the browser, Copy revision prompt is available from both the in-app review page and the shared page. The copied prompt follows the current UI language, and it tells the AI that some question comments should be answered without changing the HTML.

If something doesn't work, check the MCP troubleshooting section.