Skip to content
LiveFoliodocs
Back

MCP Overview

Connect AI agents to LiveFolio via the Model Context Protocol — publish, version, and manage folios programmatically.

What is MCP?

The Model Context Protocol (MCP) lets AI coding agents interact with LiveFolio directly. Instead of copy-pasting HTML, your agent publishes folios, updates them, reads feedback, and applies design systems — all through standard tool calls.

Architecture

AI Agent (Claude, Cursor, Copilot, Gemini CLI)
    │
    │  JSON-RPC 2.0 over Streamable HTTP
    │  Auth: Bearer API key
    │
    ▼
LiveFolio MCP Server  (/api/mcp)
    │
    ├── list_projects           → Discover folios
    ├── get_project             → Full details + files + comments
    ├── create_project          → Publish a new folio
    ├── update_project          → Edit and create a version
    ├── get_curated_brief       → Human feedback summary
    ├── get_active_design_system → Design specifications
    ├── manage_sharing          → Publish / privacy / access key
    ├── manage_listing          → Explore listing + license
    ├── search_marketplace      → Browse Explore
    ├── buy_project             → Checkout URL relay
    ├── archive_folio           → Hide a folio (reversible, not deleted)
    ├── unarchive_folio         → Restore it as a draft
    ├── list_workspaces         → Workspace folders
    ├── manage_workspace        → Create / update / move / archive folders
    └── manage_member           → Invite / roles / remove

How It Works

  1. You get an API key from Settings → API Keys
  2. You add the MCP config to your agent (one-time, 30 seconds)
  3. You ask your agent to "create a folio" or "update my project"
  4. The agent calls MCP tools — no manual API requests needed

Connecting Your Agent

Add this to your agent's MCP configuration:

{
  "mcpServers": {
    "livefolio": {
      "type": "http",
      "url": "https://livefolio.cloud/api/mcp",
      "headers": {
        "Authorization": "Bearer lf_live_xxxxxxxxxxxx"
      }
    }
  }
}

Per-client snippets (Claude Code CLI, Claude Desktop, Cursor, ZCode, Gemini CLI) are in the Quickstart. Get your API key and exact URL from the Integrations page (/connections).

Available Tools

ToolWhat it does
list_projectsList all folios in your workspace with IDs, titles, and stats
get_projectFull folio details: files, versions, comments, visibility, analytics
create_projectPublish a new folio with HTML, title, and design options
update_projectEdit files and create a new version with a commit message
delete_projectPermanently delete a folio (confirmed: true)
archive_folio / unarchive_folioHide a folio everywhere public — or restore it as a draft. Nothing is deleted
duplicate_projectCopy a folio into your account (grant-aware)
get_curated_briefStructured markdown brief from all open reviewer comments
get_active_design_systemComplete design spec: theme, palette, typography, grid, animations
add_comment / moderate_comment / add_reactionAdd, resolve/delete, and react to feedback
manage_sharingPublish/privacy/access key — no version bump
manage_paid_accessPrice, preview, and post-purchase settings
manage_listingExplore listing, license, and eligibility
search_marketplaceBrowse the public Explore gallery
buy_project / get_purchasesStart a purchase (URL relay) and track grants
manage_seller_accountStripe Connect status or onboarding
list_workspaces / manage_workspaceThe folders that organize folios — including archiving a folder and everything in it
manage_memberInvite, change roles, or remove teammates
manage_profile / claim_handle / follow_profileProfile, @username, and follows

What You Can Ask Your Agent

  • "List my LiveFolio projects"
  • "Create a folio called 'Pitch Deck' with this HTML"
  • "Update the footer on my folio to match the new brand colors"
  • "Show me the feedback on the Q3 Report"
  • "Apply the Cobalt Ocean design system to my project"

The agent handles all the MCP tool calls. You just describe what you want.

auth.md Compatible

LiveFolio is auth.md compliant. Agents can autonomously register and acquire API keys on behalf of users — no dashboard interaction required. See Authentication for the full protocol.

Next Steps