MCP

Fontana Files exposes a first-party Model Context Protocol server on your tenant origin at /_fontana-files/mcp (Streamable HTTP). Agents and external clients work with Collections: git-backed folders of files with per-Collection rbac.yaml ACL. A deploy-seeded MCP connection appears on AI → Tools as Fontana Files.

Tool catalog

Tool	What it does
ffs_list_collections	List Collections the caller can read
ffs_create_collection	Create a Collection (slug + initial rbac.yaml)
ffs_delete_collection	Delete a Collection (slug becomes reusable)
ffs_read_file	Read a UTF-8 file (path relative to the Collection file root)
ffs_write_file	Write or replace a file
ffs_list_files	List files and folders under a path
ffs_delete_file	Delete a file or empty folder
ffs_history_log	Git log for a path or whole Collection (read_history)
ffs_history_show	Show one commit (read_history)
ffs_history_revert_path	Revert a path to a prior commit (write)
ffs_history_revert_collection	Revert an entire Collection (write)

File API paths are relative to the Collection file root (do not prefix data/ on the wire).

Collection ACL, fail closed

Every tool call is evaluated against the Collection rbac.yaml for the signed-in user. Your role and team membership determine read, write, and history access. Calls without valid user context fail closed.

Tenant endpoints

On your tenant Flow origin:

• Health: https://<tenant>.<baseDomain>/_fontana-files/health (no auth)
• MCP (Streamable HTTP): https://<tenant>.<baseDomain>/_fontana-files/mcp

In Flow: enable the seeded Fontana Files connection on an agent from AI → Tools. Flow runs tool calls as the signed-in user.

External MCP clients (Cursor, ChatGPT)

Use a personal access token (PAT) to connect external MCP clients to your tenant’s public /_fontana-files/mcp endpoint. PATs authenticate as you; Collection ACL follows your role and team grants.

On AI → Tools, select the seeded Fontana Files MCP. Flow shows copyable URL, Authorization header, and Cursor JSON for ChatGPT, Claude, Cursor, and other Streamable HTTP clients. Create a PAT under Admin → Personal access tokens and paste the full fnt_pat_… value into your client config.

Cursor

{
  "mcpServers": {
    "fontana-files": {
      "url": "https://<tenant>.<baseDomain>/_fontana-files/mcp",
      "headers": {
        "Authorization": "Bearer fnt_pat_…"
      }
    }
  }
}

After editing MCP config, run Developer: Reload Window in Cursor (or fully quit and reopen).