FAQ

Frequently asked questions about LiveFolio — folios, sharing, MCP, integrations, and troubleshooting.

General

What is LiveFolio?

LiveFolio is a publishing platform for interactive HTML documents. It replaces PDFs and slide decks with living, shareable web pages that support versioning, comments, and reactions.

How do I get started?

Folios

What can a folio include?

HTML, CSS, JavaScript, and binary assets (images, fonts) encoded as base64 Data URLs.

Is there a size limit?

Check your instance's plan for specific limits. Typical limits range from 5 MB to 25 MB per folio.

Can I edit after publishing?

Yes. Every edit creates a new version. Published versions are immutable — previous work is always recoverable.

Sharing

Who can see my shared folio?

Anyone with the share URL. You can restrict access to your organization, add password protection, or set expiring links.

How do I stop sharing?

Set the folio to private in dashboard settings, or via the API.

Can I embed a folio?

Yes. Use an <iframe> pointing to the share URL.

<iframe src="https://livefolio.cloud/share/abc123"></iframe>

MCP & AI Agents

Can my AI agent publish folios?

Yes. Connect your agent via MCP — see Integrations. Your agent can create, update, and manage folios from your editor.

How do I set it up?

Go to Settings → API Keys, generate a key, and add the MCP config to your agent. Takes under a minute.

What agents are supported?

Claude Code, Cursor, GitHub Copilot, Gemini CLI — any MCP-compatible agent.

Integrations

Can I get notifications in Slack?

Yes. Connect Slack from Connections (/connections). You'll get notified about new comments, versions, and shares.

What about Discord?

Same capabilities. Connect your Discord server from the Connections page.

Troubleshooting

Folio won't publish

Check that your HTML is valid and you have publish permissions in your workspace.

Share link doesn't work

Verify the folio is set to public and hasn't been deleted. Check access control settings.

Agent can't connect

Verify the API key is valid (not revoked)
Check the MCP URL is correct
Ensure the Authorization: Bearer header is properly formatted