Claude chat
Open Claude’s connector controls, add Foliyo and complete OAuth sign-in. Enable Foliyo for the conversation before asking it to publish. If you use a custom web connector, enter https://foliyo.io/mcp.
Connect the agent you already use. Turn a proposal, report or client handover into a branded, gated page with readership tracking.
What connecting adds. Your AI tool can update a client’s page in one request, and the link stays the same. It applies your saved client setup (branding, sender and recipients) as part of that request. And repeat work needs no editor: say what changed and it publishes.
No connector? Paste it. If your AI tool can’t connect to Foliyo, or you’d rather not set it up, copy the finished HTML into Foliyo and publish from your browser. You get the same branded, gated link. Paste and publish
Hosted by Foliyo. Sign in once in each client. Your saved projects, senders, guides and audiences stay with your account. Approve mcp workspace:write to edit pages created in other clients; a restricted mcp grant keeps its existing limits.
Open Claude’s connector controls, add Foliyo and complete OAuth sign-in. Enable Foliyo for the conversation before asking it to publish. If you use a custom web connector, enter https://foliyo.io/mcp.
Run these commands, then complete browser sign-in:
codex mcp add foliyo --url https://foliyo.io/mcp
codex mcp login foliyo --scopes 'mcp,workspace:write'Or use Settings → MCP servers → Add server → Streamable HTTP. Save, restart and authenticate. The desktop app, CLI and IDE extension share host configuration.
Add to .cursor/mcp.json or ~/.cursor/mcp.json, then enable Foliyo and sign in:
{
"mcpServers": {
"foliyo": { "url": "https://foliyo.io/mcp" }
}
}Cursor CLI shares this config:
agent mcp login foliyo
agent mcp enable foliyo
agent mcp list-tools foliyoclaude mcp add --transport http --scope user foliyo https://foliyo.io/mcp
claude mcp login foliyoUse /mcp inside Claude Code to authenticate on older versions. Shared project configuration needs an explicit HTTP type:
{
"mcpServers": {
"foliyo": {
"type": "http",
"url": "https://foliyo.io/mcp"
}
}
}Add the hosted server and approve the browser sign-in. No local process or API key is needed.
Manual setup: Integrations → MCP Servers for Replit Agent → + Add MCP server. Name it Foliyo, enter https://foliyo.io/mcp, then choose Test & save.
Replit supports OAuth for custom servers and custom headers in Advanced settings. Review workspace permission during consent.
Foliyo supports static HTML and CSS-only interactions: checkbox and radio tabs, labels, dropdown controls, expandable details, anchor navigation and native popovers. IDs, radio groups, checked state and label associations are preserved. Dropdowns need your own CSS rules to change visible content.
Publisher scripts and event handlers do not run. Text, password and file inputs, textareas, and form submission are not supported. Form wrappers are removed and buttons cannot submit forms. HTTPS embeds are sandboxed.
Run preflight_html before publishing. Its prepared HTML uses the live sanitizer and reports removed or neutralized markup. Inspect that prepared page in a browser as well; preflight is not a visual test. The current policy is 2026-09-23-static-controls.
<style>#more:not(:checked) ~ .extra { display:none }</style>
<input type="checkbox" id="more">
<label for="more">Show details</label>
<section class="extra">Additional content</section>Install the Foliyo skill, then ask: “Create me a Foliyo proposal for Acme using our saved project.” The skill supplies the workflow; the MCP connection supplies the account tools.
| Agent | Save the skill as |
|---|---|
| Codex | .agents/skills/foliyo/SKILL.md |
| Cursor | .cursor/skills/foliyo/SKILL.md |
| Replit Agent | .agents/skills/foliyo/SKILL.md |
| Claude Code | .claude/skills/foliyo/SKILL.md |
These are project paths. Give your agent the skill URL and ask it to install the document in the matching directory, or copy the complete skills/foliyo directory from the source repository when that revision is available.
Your agent loads the matching project, sender, guide, audience and sharing policy before composing.
It creates responsive static HTML, includes supported assets and checks the document before publishing.
Get the live URL and PIN where applicable. Retrieve and update the source from another authorized client, keeping the same link.
Foliyo publishes static HTML. CSS, raster images and fonts can be sent as base64 assets and inlined. Script-driven charts and application screens need a static version first; Foliyo does not run arbitrary applications or backend services.
Your explicit or saved sharing policy wins. Without one, the agent can use a generated PIN and tell you, or ask one essential question. An unverified email gate records a claimed address; it does not prove identity. Publishing never implies permission to send announcement or update emails.
Download the standalone CLI from Foliyo. It needs Node 20+ and connects to the hosted service:
curl -fsSL https://foliyo.io/cli.mjs -o foliyo.mjs
node foliyo.mjs login
node foliyo.mjs tools
node foliyo.mjs publish ./report/index.html --options publish-options.json
node foliyo.mjs doctorNo npm installation is needed. Use node /absolute/path/foliyo.mjs as a stdio MCP command, or call POST /api/integration/call with a Bearer credential and {"name":"prepare_foliyo","arguments":{}} from a shell.
The 0.4.0 source CLI bridges to the same hosted server. Until npm publication is confirmed, build it from a checkout with Node 20+:
npm --prefix mcp install
npm --prefix mcp run build
node mcp/dist/server.js login
node mcp/dist/server.js tools
node mcp/dist/server.js call brand_guide --json context.json
node mcp/dist/server.js publish ./report/index.html --options publish-options.json
node mcp/dist/server.js doctorcontext.json can contain {}. Publishing options can contain {"title":"Client update","gate":"pin"}. call TOOL --json - reads stdin. With no arguments, the CLI starts a stdio bridge. After installing version 0.4.0, use foliyo in place of node mcp/dist/server.js.
Use PUBLISH_API_KEY for an explicit key and PUBLISH_API_URL to choose a backend. Keep credentials in the environment or a secret store.
A generic third-party bridge forwards your client's MCP calls to hosted Foliyo:
{
"mcpServers": {
"foliyo": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://foliyo.io/mcp",
"--transport", "http-only",
"--static-oauth-client-metadata",
"{\"scope\":\"mcp workspace:write\"}"]
}
}
}The default OAuth flow needs a browser and loopback callback. Bridge documentation.
Inspect the tool list and ask your agent to load Foliyo context with prepare_foliyo or brand_guide. Preflight a small document, publish it with a PIN, then retrieve it with get_page. An update denied in a second client may require reconnecting with workspace:write.
Claude chat and Cursor editor setup references were checked on 15 October 2026. Other client instructions retain their earlier documentation baseline; consult the linked provider documentation for current controls. Protocol compatibility is separate from live client verification; these instructions do not claim end-to-end testing of the current Cursor or Replit UI against this deployment.