curl -X POST https://api.easl.dev/publish \
  -H "Content-Type: application/json" \
  -d '{"content": "# Hello World\nSome **markdown** here.", "contentType": "text/markdown"}'

# → https://warm-dawn.easl.dev

What happens

easl auto-detects your content and renders it with the right interactive viewer:

• CSV → sortable table with sticky headers and alternating rows
• Markdown → styled prose with headings, code blocks, and tables
• JSON → collapsible tree with syntax highlighting
• Mermaid → rendered diagram (flowcharts, sequence diagrams, etc.)
• SVG → sanitized, zoomable viewer
• HTML → served as-is
• PDF → embedded viewer
• Images → responsive centered viewer

8 formats. Zero config. All auto-detected.

Quick Start

CLI

curl -fsSL https://easl.dev/install.sh | sh

easl publish report.md
# => https://calm-river.easl.dev

easl publish data.csv --title "Q4 Results" --open
cat logs.json | easl publish --type json
easl list

MCP Server

Add to your MCP config (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "easl": {
      "command": "npx",
      "args": ["-y", "@easl/mcp"]
    }
  }
}

Then just ask your agent:

"Publish this CSV as a shareable table"

"Turn this markdown into a beautiful page"

Agent Skill

Give your agent built-in knowledge of easl — content types, viewers, best practices:

npx skills add AdirAmsalem/easl

Works with Claude Code, Codex, Cursor, ChatGPT, Gemini CLI, and more.

With curl

curl -X POST https://api.easl.dev/publish \
  -H "Content-Type: application/json" \
  -d '{"content": "Name,Role\nAlice,Engineer\nBob,Designer", "contentType": "text/csv"}'

Supported Formats

MCP Server

The MCP server gives AI agents first-class publishing capabilities through the Model Context Protocol.

Available Tools

Environment

REST API

Base URL: https://api.easl.dev

Full API docs: easl.dev/docs

Architecture

easl runs on Cloudflare's edge network as a single Worker:

• Hono router handles API requests, landing page, docs, and wildcard subdomain serving
• R2 stores uploaded files
• D1 (SQLite) tracks site metadata and version history
• KV caches rendered HTML shells for fast serving

When a site is requested (e.g. warm-dawn.easl.dev), the Worker detects the file type, generates an HTML shell with the right interactive viewer, and embeds the raw data for client-side hydration.

Monorepo Structure

packages/
  worker/        → Cloudflare Worker (Hono routes, smart rendering, serving)
  cli/           → CLI (npm: @easl/cli)
  mcp-server/    → MCP server (npm: @easl/mcp, stdio transport, 5 tools)

Self-Hosting

Prerequisites: Node.js ≥ 20, a Cloudflare account, and wrangler.

1. Clone and install

   git clone https://github.com/AdirAmsalem/easl.git
   cd easl
   pnpm install

2. Create Cloudflare resources

   # Create KV namespace
   wrangler kv namespace create SITES_KV
   
   # Create R2 bucket
   wrangler r2 bucket create easl-content
   
   # Create D1 database
   wrangler d1 create easl-db

3. Configure — Update packages/worker/wrangler.toml with your resource IDs and domain

4. Initialize the database

   cd packages/worker
   pnpm db:migrate

5. Deploy

   pnpm deploy

Development

pnpm install          # Install dependencies
pnpm dev              # Start local dev server (wrangler dev)
pnpm test             # Run tests
pnpm build            # Build all packages

Local dev uses path-based routing instead of subdomains:

• API endpoints: http://localhost:8787/publish, /sites
• View sites: http://localhost:8787/s/:slug
• Docs: http://localhost:8787/docs

Contributing

Contributions are welcome! Whether it's bug fixes, new viewer types, or documentation improvements.

1. Fork the repo
2. Create your branch (git checkout -b my-feature)
3. Make your changes
4. Run tests (pnpm test)
5. Open a PR

Looking for a place to start? Check out the good first issues.

License

MIT