Live data boards · published by your agent
Your agent did the analysis. This is the link that keeps it alive.
CruxBoards hosts the boards your agent publishes over MCP — live data, one link. Push your series, compose a board, share it. When the numbers change, the link doesn't.
Free to publish. Viewers never need an account.
This is a share page, not a screenshot — open the real one
Why this exists
An analysis today has three fates. Two of them lose.
Chat artifacts that read your data stay locked to your machine — sharing one would hand the viewer your credentials. So everything shared becomes an export, frozen the moment it leaves. CruxBoards is built the third way: your agent pushes the data to us, so the board needs nobody's credentials to render — not yours, not the viewer's. Live and shareable stop being a trade-off.
It stays in the chat
Live artifacts refresh for you — and can't be shared at all. Your colleague sees it over your shoulder or not at all.
Pull architecture: the page runs on your credentials.
It goes out as an export
Screenshot, PDF, static page. Shareable — and wrong by next Tuesday, with no one notified.
Frozen at publish; every update is a re-send.
It lives at a link
Your agent pushes data here. The board renders live for anyone with the link — revocable, optionally password-locked.
Push architecture: the board carries no one's credentials.
How it works
Three steps, all of them in your agent
Works with anything that speaks MCP — Claude Code, Codex, Cursor, or your own harness. You never upload a CSV to a web form; your agent does the pushing.
Connect your agent
Sign in, mint a token, paste the config. The token scopes everything to your account.
{
"mcpServers": {
"cruxboards": {
"type": "http",
"url": "https://cruxboards.com/mcp",
"headers": { "Authorization": "Bearer crux_…" }
}
}
}
Push the numbers your analysis produced
Normalized points, one value per period. A period with no value stays absent — never a fake zero.
› tell your agent: "Push our weekly lane costs to CruxBoards" push_series { seriesId: "lane-costs", unit: "$/load", source: "our TMS export", points: […52 weeks] }
The source string you push is printed on the board, verbatim. Choose honestly.
Share the link
Compose the board (your agent or the editor — both write the same spec), then mint the link.
publish_share { boardId } → https://cruxboards.com/s/shr_a1b2c3… live · revocable · password-protectable (Pro)
Next week your agent pushes fresh numbers. Everyone's link is already current.
Trust, structurally
Every board says where its numbers came from — and the page can't take it off.
Provenance on a CruxBoards page isn't a courtesy the author extends. It's a required field of the render: the server injects it, the renderer has no way to omit it. What your viewers see is always labeled — which source, pushed when — including the label "User-provided" when the numbers are yours.
For the person you send it to
Viewers just click
- ✓No account, ever. The link is the whole ceremony — it opens for anyone you send it to.
- ✓Always the current numbers. They see what the data says today, not what it said when you exported.
- ✓You stay in control. Revoke a link and it dies everywhere, instantly. Password-lock it for client work.
Pricing
Free to publish. Pro when it's client-facing.
- ✓Unlimited boards and public share links
- ✓Live data, revocable links, full editor
- ✓View counts on every link
- ·Boards carry a "Made with CruxBoards" mark
- ✓Everything in Free
- ✓No watermark — your boards, your name only
- ✓Password-protected links for client deliverables
- ✓View analytics over time, not just a counter
Pro is in early access — request it from your dashboard after signing in.
Questions
The honest fine print
What does the person I share with need?
A browser. No account, no app, no login. If you set a password, they need the password — share it through a separate channel.
What happens when my data changes?
Your agent pushes again — same series id, fresh points. Every link you ever minted shows the new numbers on next load. Nothing to re-send.
Can I take a shared link back?
Yes. Revoke it and it's a dead link everywhere, immediately. Revoked links are indistinguishable from links that never existed.
Whose data is it, and what about licensed sources?
Yours. You push it, you can delete it, and every board states its sources verbatim. If your numbers come from a licensed feed, publishing them to a shared board is on you — the boards make the source visible precisely so that question is never hidden.
Which agents work?
Anything that speaks MCP over HTTP: Claude Code, Claude Desktop, Codex, Cursor, or a harness you wrote yourself. CruxBoards is deliberately vendor-neutral — the token is the only thing that's ours.