Skip to main content
KiwiFS Cloud is the hosted version of KiwiFS. It handles workspace provisioning, authentication, billing, and multi-tenant routing so you can skip deployment and go straight to building.

How it works

Your agent / app                   KiwiFS Cloud
─────────────────                  ──────────────────────
kiwi_sk_* or OAuth  ──────────▶   api.kiwifs.com (proxy)


                                   KiwiFS instance
                                   (your workspace)
Cloud authenticates your request and forwards it to the KiwiFS instance that backs your workspace. All self-hosted KiwiFS features — REST, MCP, search, versioning, drafts, and more — are available through the cloud proxy.

Authentication

Every workspace has a kiwi_sk_* API key. Pass it as a Bearer token:
curl https://api.kiwifs.com/api/workspaces/eng-handbook/file?path=README.md \
  -H "Authorization: Bearer $KIWI_API_KEY"
Get your key from Settings → API Key in the workspace UI, or via the CLI:
kiwifs login
kiwifs connect eng-handbook

REST API

Base URL: https://api.kiwifs.com/api/workspaces/{slug} The cloud proxy exposes the same endpoints as self-hosted KiwiFS. Key endpoints:
MethodPathDescription
GET/treeList workspace files
GET/file?path=README.mdRead a file
PUT/file?path=README.mdCreate or update a file
DELETE/file?path=README.mdDelete a file
GET/search?q=authFull-text search
POST/search/semanticVector search
GET/query?q=TABLE ...DQL query
GET/versions?path=...Git history
GET/contextAgent playbook + schema
curl "https://api.kiwifs.com/api/workspaces/eng-handbook/file?path=README.md" \
  -H "Authorization: Bearer $KIWI_API_KEY"
For the full endpoint reference, see the REST API documentation. All endpoints documented there work under the cloud base URL.

MCP

The MCP endpoint for a cloud workspace is:
https://api.kiwifs.com/api/workspaces/{slug}/mcp
For agents that support MCP OAuth (Claude Desktop, Cursor, etc.):
{
  "mcpServers": {
    "kiwi": {
      "url": "https://api.kiwifs.com/api/workspaces/eng-handbook/mcp"
    }
  }
}
The agent will open a browser login flow on first connection.
All 60+ MCP tools are available through the cloud endpoint. See MCP tool reference.

CLI setup

# Authenticate with KiwiFS Cloud
kiwifs login

# Generate MCP config for a workspace
kiwifs connect <workspace-slug>

# Check who you're logged in as
kiwifs whoami

# Log out
kiwifs logout
kiwifs connect detects your MCP client (Claude Desktop, Cursor, etc.) and writes the appropriate config file.

API key management

OperationHow
View keySettings → API Key in workspace UI
Rotate keySettings → API Key → Rotate or POST /api/workspaces/{slug}/rotate-key
ScopeKeys are scoped to a single workspace
Formatkiwi_sk_ followed by 32 URL-safe characters
API keys are shown once on creation or rotation. Store them securely — KiwiFS Cloud stores only a hash and cannot recover the plaintext.

Public workspaces

Workspaces can be set to public or unlisted visibility. Public workspaces expose read-only endpoints without authentication:
# Public tree
GET /api/workspaces/{slug}/public/tree

# Public file read
GET /api/workspaces/{slug}/public/file?path=README.md

# Public search (public workspaces only)
GET /api/workspaces/{slug}/public/search?q=auth

# Published page (any visibility)
GET /api/workspaces/{slug}/public/page/{path}

Differences from self-hosted

FeatureSelf-hostedCloud
Authconfigurable (none, apikey, perspace, OIDC)API key + MCP OAuth 2.1
Base URLhttp://host:3333/api/kiwihttps://api.kiwifs.com/api/workspaces/{slug}
Multi-spaceX-Kiwi-Space header or URL prefixone workspace per slug
Alternate protocolsNFS, S3, WebDAV, FUSEMCP and REST only
OpenAPI spec/api/openapi.jsonnot exposed (use self-hosted spec)
BillingN/Amanaged via Settings → Billing

API overview

Full REST API reference (endpoints work the same on cloud).

MCP

60+ MCP tools and client setup.

Agent playbook

Agent onboarding with kiwi_context.

Quickstart

Self-hosted quickstart for local development.
Last modified on May 30, 2026