MCP-native
Reports and proposals — shared as one HTML document with charts and analysis, not a wall of text. Your team comments in place; revision prompts go back to the AI in one click.
$ claude mcp add --transport http traypage http://localhost:3000/api/mcpSet up in 2 minutes
Competitive Analysis Q3
Strategy Team · v3
the domestic market is growing at +18% CAGR, leaving ample room to enter.
Fig. 1 — Domestic market size
“the domestic market is growing at +18% CAGR”
Yuki · 12 min ago
Please add the source as a footnote
Mori · 8 min ago
Competitor B's October price change isn't reflected
Don't stop at “generated”. See it, question it, fix it — and all you do is chat.
Your AI tool
Claude Code / Claude / Cursor, etc.
TrayPage
Home for deliverables + reviews
Your team
Opens in the browser
MCP is the open standard that lets AI tools operate external services directly. Connect once — after that, you just ask in chat.
01
Publish
Just ask in chat. The AI assembles the HTML and publishes it. No build, no deploy.
02
Share
Send the link. Five visibility levels keep it inside the company.
03
Comment
Select any number or claim in the document and question it right there.
04
Revise
Comments become one revision prompt for the AI. Loop until the team is convinced.
01 — Publish
Put together the Q3 competitive analysis report and share it with the team
I created the report and published it.
02 — Share
03 — Comment
💬 Yuki commented: “Please add the source as a footnote”
04 — Revise
Apply the comments
Picked up the revision prompt and published v2 ✓
Built-in mechanisms to safely host arbitrary AI-generated HTML.
One click to share with anyone signed in on your company domain. Circulate reports internally without resorting to public links.
Five visibility levels. Closed by default.
Artifact HTML runs inside a CSP sandbox and can never touch your app cookies or session. In production it is served from a separate domain for an extra layer of isolation.
CSP sandbox — scripts cannot escape
Audit log
Every publish, share, permission change, and comment is recorded.
Approval workflow
in_review → approved → published. Only versions your team has checked go live.
OAuth 2.1 MCP access
MCP clients are scoped per workspace and approved via explicit consent.