NEW MCP server v0.7 — publish from inside Claude

The permanent home
for everything your team builds
with Claude.

Folio is an open-source artifact marketplace for the dashboards, tools, calculators, and reports your team generates as Claude HTML artifacts. Publish them from inside Claude. Discover what others built. Fork anything in one prompt.

$npx folio init --connect-claudeView the marketplace →Star on GitHub
Active orgs
340+ self-hosting
Published artifacts
12,406
License
MIT fork freely
Stack
postgres · next · MCP
The marketplace

Every artifact your team has ever built, in one place.

This is not a screenshot. It's a real instance, indexing 340 organizations' public artifacts. Browse, fork, or run any of these with one click.

folio.acme.dev/marketplace
⌘ K
All12,406
Trending
New this week42
Your org186
Staff picks
Dashboard · 1920×1080⑂ 312
Q2 Pipeline Health
Live ARR funnel pulled from Salesforce + Linear. Auto-refreshes daily. Uses your org's color palette.
salesforcefinanceforked 312×
@priya · revops·▶ 8.4k runs
Form · responsive⑂ 41
Procurement intake v3
Routes vendor requests to legal, IT, and finance based on dollar amount and data class. SSO-aware.
internalapprovalsokta
@marcus · it·▶ 1.2k runs
Visualization · interactive⑂ 891
Org chart, but living
A Workday-fed org chart with tenure, on-call rotations, and reporting depth. Filter by team or location.
peopleworkdaystaff pick
@leon · platform·▶ 24.1k runs
Report · weekly⑂ 56
Incident postmortem template
Generates a structured PIR from a PagerDuty incident ID. Ships with severity-aware sections.
srepagerduty
@ines · sre·▶ 612 runs
Calculator · single-page⑂ 1.1k
Cloud spend what-if
Drag region, instance class, and reserved-vs-spot mix. Charts cost delta against last month's bill.
finopsawstrending ↑
@kenji · platform·▶ 19.7k runs
Tool · interactive⑂ 78
RFC review router
Drop an RFC link in. Returns the right reviewers for security, infra, and design based on file paths touched.
enggithub
@asha · eng-platform·▶ 3.0k runs
How it works

Publish from Claude. Discover anywhere. Fork in a sentence.

The whole loop runs on a single MCP server. No new tab, no separate publishing flow, no migrating off your existing Claude workflow.

01 · Publish

From Claude, in one message.

Once you've connected the Folio MCP server, Claude knows how to publish. Tell it to ship the artifact and it's live, versioned, and indexed.

You
Publish this dashboard to folio under /revops as "Q2 Pipeline Health". Make it discoverable by the whole org.
Claude
Publishing to folio.acme.dev/revops folio.publish_artifact ✓ live folio.acme.dev/revops/q2-pipeline
02 · Discover

The marketplace is the homepage.

Browse trending, staff picks, and what your team published this week. Tag, filter, and search across every artifact in your org — and across every public org if you want.

// search.ts
await folio.search({
query: "runway calculator",
org: "acme",
sort: "forks_7d",
limit: 12
})
// → 4 artifacts, 1 staff pick, 312 forks combined
03 · Fork & Remix

Anyone's artifact, your data.

Fork an artifact straight back into a Claude conversation. Swap data sources, restyle, extend — the lineage stays linked so improvements can flow back upstream.

@priya/q2-pipeline
@kenji/finops-fork
@you/your-fork ✦
MCP integration

One server. Six tools. Every Claude conversation suddenly knows about your artifacts.

Folio ships as a Model Context Protocol server. Drop it into your Claude config, sign in once, and the publish/fork/search loop is available in every conversation.

The MCP server is the product surface.

No browser tab to switch to. No Slack handoff. Folio works exactly where your team is already building — inside Claude.

publish_artifact — ship the current artifact with a slug, tags, and visibility scope.
search — semantic + keyword search across your org and the public registry.
fork_artifact— pull any artifact's source straight into the active conversation as a starting point.
describe, list_versions, diff — auto-changelog when an artifact changes hands.
~/.config/claude/mcp.jsonedited 2m ago
{
  "mcpServers": {
    "folio": {
      "command": "npx",
      "args": ["-y", "@folio/mcp"],
      "env": {
        "FOLIO_HOST": "https://folio.acme.dev",
        "FOLIO_TOKEN": "flo_…sso"
      }
    }
  }
}

# Verify the connection
$ folio doctor
  ✓ MCP handshake     OK
  ✓ SSO (okta)        OK · 286 members
  ✓ Indexer           OK · 186 artifacts
  ✓ Webhooks → Slack  OK
Built for teams

Boring on purpose where it matters.

Folio is the missing layer between "we built something useful in Claude" and "the rest of the company can find it next quarter."

Versioned by default

Every publish is a new immutable version. Roll back, diff, and fork from any point in history.

Scoped visibility

Private to you, your team, your org, or the public registry. Switch with one prompt.

SSO & SCIM

Okta, Google, Entra. SCIM for groups maps directly to artifact ACLs.

Audit log

Who published what, who forked it, who ran it. Streamable to your SIEM.

Sandboxed runtime

Artifacts execute inside a sandboxed iframe with capability-based access to org data.

Slack & webhook hooks

New publish in #revops? Drop a card with a one-click run button right in the channel.

Open source · MIT

Run the whole thing
on your own metal.

Folio is a Next.js app, a Postgres database, and an MCP server. That's it. Self-host on your own VPC, point your team's Claude config at it, and you're done. We also offer Folio Cloud if you'd rather we run it.

runtime node 20+ · postgres 15+ deploy docker · kamal · vercel auth okta · google · entra · github storage s3-compatible (any) install npx folio init size ~14 MB compiled · 1 binary license MIT — fork the registry too