Use shell commands or publish a local file
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 doctor
No 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 doctor
context.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.
Connect a stdio-only client
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.
Check the connection
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.
Native setup follows official documentation checked on 5 September 2026. 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.