Fillo

헤드리스 폼 인프라 — 폼이 제품 내에서 네이티브로 렌더링되고(iframe 없음), 파일은 사용자가 소유한 스토리지에 브라우저에서 직접 업로드되며, 코딩 에이전트가 MCP를 통해 이를 프로비저닝, 게시, 조회할 수 있습니다.

문서

Fillo — forms inside your product, with your UI.

Docs · Guides · Agents · Changelog

npm version MIT license

The Fillo MCP server. It gives a coding agent the full Fillo loop — provision a workspace, scaffold a form into the host repo, publish it, and query its responses — without leaving the session, authenticated exactly like a human CLI user.

Install

One click, if your editor supports it:

Add to Cursor Add to VS Code

Claude Code:

claude mcp add fillo -- npx -y @usefillo/mcp

Any other MCP client: run npx -y @usefillo/mcp over stdio. Set FILLO_API to point at a non-production deployment.

Credentials

The server reads the same credentials the CLI writes to ~/.fillo/config.json, or from the environment:

  • FILLO_TOKEN — a fcli_… login token (from npx @usefillo/cli login). Authenticated tools (fillo_list_forms, fillo_publish_form, and trusted pushes to a claimed workspace), plus local project selection with an ordinary login. File-request pushes remain draft/staged for review.
  • FILLO_PK — a pk_… publishable key. fillo_provision_workspace mints one and saves it for you.
  • FILLO_API_KEY — a fsk_… project API key, minted in Settings → Connections of a claimed workspace. Required by the response tools.
  • FILLO_API — overrides the origin (default https://fillo.so).
  • FILLO_CONFIG_DIR — overrides the config directory (default ~/.fillo).

The server never prints login tokens, API keys, or claim tokens into the transcript. The pk_ publishable key is safe to surface (it lives in browser code), so fillo_provision_workspace returns it for you to wire into the app's public env. Provisioning also makes that temporary project the active local MCP context, so an older saved account login cannot receive the next push. Selecting a project switches the context back to the account.

Tools

ToolAuthWhat it does
fillo_provision_workspacenone (needs an email)Create an unclaimed preview workspace, return its pk_ key and caps, and email its claim link.
fillo_whoamilogin token or pk_Report the active credential, workspace, and project.
fillo_list_projectsordinary login tokenList projects in the current workspace and mark the current selection.
fillo_create_projectordinary login tokenCreate and select an isolated project and save its pk_ key.
fillo_select_projectordinary login tokenSelect by id, slug, or unique exact name and update local project state.
fillo_push_formlogin token or pk_Create or update a form from a schema + handle; file requests remain draft/staged until explicit publish.
fillo_publish_formlogin tokenTake a draft or staged changes live after review; return the exact storage setup link when blocked.
fillo_list_formslogin tokenList the project's forms.
fillo_get_formnone (published)Fetch a published form's schema, theme, and capabilities.
fillo_search_examplesnoneSearch the curated Fillo example library.
fillo_docsnoneFetch a Fillo docs page as Markdown by topic.
fillo_list_responsesfsk_ API keyList a form's responses (claimed workspaces only).
fillo_get_responsefsk_ API keyFetch one response (claimed workspaces only).
fillo_response_summaryfsk_ API keySummarize a form's responses without reading every row (claimed workspaces only).
fillo_claim_statuspk_Report the provisioned workspace's caps and claim deadline.

There are no delete tools. Write annotations still use the conservative worst-case hint because a push can replace draft state and a publish can replace the public schema. Every tool is a thin wrapper over Fillo's public HTTP API — the server never touches the database and imports no app code, so workspace scoping, rate limits, and validation stay in one place.

The three project tools are local-only and require the general token minted by fillo login. A project-specific handoff and a hosted remote-MCP OAuth grant remain pinned to the project a human approved. Selecting locally also clears cached preview and fsk_ state from the prior project; replace any FILLO_PK or FILLO_API_KEY environment overrides yourself.

Projects are sites/apps beneath one billed workspace. They isolate forms, publishable/API keys, allowed origins, respondent identities, and agent authority. Workspace membership, billing, storage connections, and usage totals remain shared.

Links

MIT licensed.