First share in 60 seconds
Get from zero to a shareable URL in under a minute. No config files. No infrastructure to manage.
Sign up
Go to pail.thalos.ai/app/login and sign in with GitHub or a magic-link email. No password required.
Copy your API key
After sign-in you land on the welcome page. Copy your API key — it is shown once. Store it in your shell environment or a secrets manager.
export PAIL_API_KEY="pk_..."Install pail in your agent
Pick your client and run the install command.
claude mcp add --transport http pail https://pail.thalos.ai/mcp \
--header "Authorization: Bearer $PAIL_API_KEY"Add to .cursor/mcp.json in your project root:
{
"mcpServers": {
"pail": {
"url": "https://pail.thalos.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}codex mcp add pail \
--url https://pail.thalos.ai/mcp \
--header "Authorization: Bearer $PAIL_API_KEY"Open Windsurf MCP settings and add a new server entry:
{
"name": "pail",
"url": "https://pail.thalos.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}Open Cline MCP settings and add a new HTTP server:
{
"pail": {
"url": "https://pail.thalos.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}Use the share tool
In Claude Code (or any connected client), ask your agent to share something:
share a file called test.md with content "# Hello from pail"
The agent calls the share tool and returns a URL.
Open it in your browser — you will see rendered Markdown.
Teach your agent when to use pail
Put pail preferences in your project AGENTS.md so the
agent knows when to produce a URL instead of pasting a wall of output
into chat.
Balanced default
## Pail
The pail MCP server is available. Use it when a URL is a better handoff than
chat text or a local-only path.
Use share for generated docs, reports, CSVs, notebooks, logs, screenshots,
and other artifacts I should open in a browser.
Use preview for static HTML/CSS/JS mocks or built frontend output I should
click through, especially when local auth or setup blocks review.
Use compare for A/B options, ask/review for decisions or approvals, and status
for long-running work.
Frame visual mocks and previews in clearly labeled viewports or panels so
separate states do not read as one accidental page.
Keep short explanations in chat. Do not upload secrets, credentials, private
customer data, or raw database dumps. Use short TTLs and add an access token
for sensitive-but-shareable work.Artifact-heavy projects
## Pail
Use pail for artifacts I ask you to share: diagrams, screenshots, reports,
notebooks, CSVs, generated docs, long logs, and built previews. Prefer pail
URLs over pasting long generated content into chat. When there are multiple
reasonable options, create a compare link. Frame mocks in labeled panels when
showing multiple states.Async or overnight work
## Pail
When a task runs for more than a few minutes, create a pail status page and
send me the URL. Use pail ask/review links when you need a decision from me
before continuing. If you produce a visual mock or built preview while I am
away, send it as a pail preview.Quiet by default
## Pail
Use pail only for handoffs I need to open away from my terminal: diagrams,
mocks, status pages, review links, comparisons, and documents I explicitly
ask you to send. Keep routine summaries in chat.Client install instructions
pail works with any MCP-compatible client. The server is at
https://pail.thalos.ai/mcp. All clients use HTTP
transport with an Authorization: Bearer header.
Claude Code
claude mcp add --transport http pail https://pail.thalos.ai/mcp \
--header "Authorization: Bearer $PAIL_API_KEY"Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"pail": {
"url": "https://pail.thalos.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}Codex CLI
codex mcp add pail \
--url https://pail.thalos.ai/mcp \
--header "Authorization: Bearer $PAIL_API_KEY"Windsurf
Add to your Windsurf MCP config:
{
"name": "pail",
"url": "https://pail.thalos.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}Cline
Add to Cline MCP settings:
{
"pail": {
"url": "https://pail.thalos.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}Tool reference
pail provides 10 tools over MCP. Every tool is available on all plans
except preview, which requires Pro or higher.
Recipes
Copy-paste patterns for real workflows. Each recipe is a runnable transcript with actual MCP calls.
overnight-agent-approval
Let an overnight agent pause for your go/no-go before pushing to production.
read recipe →deploy-todo
Non-blocking reminder: smoke-test /checkout before the client call.
read recipe →show-diff-before-merge
Review an agent-generated patch with syntax highlighting and line comments.
read recipe →mermaid-diagram-slack
Paste a pail URL into Slack and have the diagram appear inline.
read recipe →stash-oauth-token
Hand a short-lived secret from Agent A to Agent B without touching disk.
read recipe →watch-migration
Live progress page with row counts and a clear success/failure state.
read recipe →voice-note-context
Drop notes on your phone; the agent picks them up at the next run.
read recipe →preview-react-site
Build → bundle → live URL in one tool call. No Vercel, no dev server.
read recipe →API Reference
The full REST API is documented via OpenAPI.
Interactive documentation is available at
/api/docs. All admin endpoints require an
Authorization: Bearer <key> header. The same key
works for both the REST API and the MCP server.
SDK
A Python SDK is planned. For now, use the MCP server from any MCP-compatible client, or call the REST API directly.
The REST API follows standard HTTP conventions. Uploads accept
multipart/form-data. All responses are JSON with
ISO-8601 timestamps.