Integrations

Connect AI coding agents, Slack, and Discord to LiveFolio — publish folios from your editor, get notifications in chat.

Integration Hub

LiveFolio connects to your existing tools so you can publish folios without leaving your workflow. All integrations are managed from the Connections page (/connections).

AI Agent (MCP)

Connect your coding agent to publish folios directly from your editor. Your agent can create, update, list, and manage folios — just ask it.

One-Click Setup

Go to Connections (/connections)
Copy your MCP endpoint URL and API key
Paste into your agent's MCP configuration
Done — your agent can now publish folios

Supported Agents

Agent	How to connect
Claude Code	Add to `~/.claude/claude_desktop_config.json` or `.mcp.json`
Cursor	Add to Cursor MCP settings
GitHub Copilot	Add to Copilot MCP configuration
Gemini CLI	`gemini mcp add livefolio {your-mcp-url}`

What Your Agent Can Do

Ask your agent things like:

"List my LiveFolio projects"
"Create a LiveFolio folio called 'Q3 Report' with this HTML"
"Update the header color on my folio to blue"
"Show me the feedback on my latest folio"

The agent calls the MCP server automatically. No manual API requests needed.

Manual MCP Configuration

{
  "mcpServers": {
    "livefolio": {
      "url": "https://livefolio.cloud/api/mcp",
      "transport": "sse",
      "headers": {
        "Authorization": "Bearer lf_agent_xxxxxxxxxxxx"
      }
    }
  }
}

Generate your API key from Settings → API Keys.

Slack

Get folio activity notifications directly in Slack:

Go to Connections → Slack
Click "Connect Slack"
Authorize the LiveFolio app in your workspace
Choose which channels receive notifications

Notifications include:

New comments on your folios
New versions published
Folio sharing events

Discord

Same capabilities as Slack, for Discord communities:

Go to Connections → Discord
Click "Connect Discord"
Authorize the LiveFolio bot in your server
Configure notification channels

API Keys

Manage programmatic access from Settings → API Keys:

Generate keys for agents, scripts, or CI/CD pipelines
Name each key descriptively (e.g., "Claude Code", "GitHub Actions")
Revoke keys instantly — all connections using that key stop working
Rotate regularly for security

Keys use the format lf_agent_xxxxxxxxxxxx and are shown only once at creation. Store them securely.

Self-Hosting?

If you're running your own LiveFolio instance, see the Self-Hosting Guide for MCP setup, tunnel configuration, and API key management specific to self-hosted deployments.