
Fillo
io.github.jacobfunch由 GitHub 帳號 jacobfunch 發布v0.11.2更新於 Oct 24, 2026
Fillo MCP server — provision, scaffold, publish, and query forms from your coding agent.
概覽
Fillo 的 MCP 伺服器讓編碼代理在 fillo.so 上建立、搭建、發布與查詢無頭表單。
- 可以做什麼
- 從代理中開通並設定 Fillo 工作區與表單,包含一次執行即連接線上工作區的 Build with AI 交接流程(依 README)。搭建並發布表單,使其可用 Fillo SDK 嵌入自家應用程式渲染。查詢表單及其送出的回覆,回覆會進入支援搜尋、下載與 CSV 匯出的結構化表格。搭配與供應商無關的 Agent Skill 建置、嵌入、設定樣式、同步並驗證 Fillo 表單。
- 適用情境
- 適合在使用 Fillo 無頭表單建置產品時,讓編碼代理不必切換到託管編輯器即可建立、發布或檢視表單與回覆。若不使用 Fillo 則幫助不大。
- 執行需求
- 遠端端點 fillo.so,或透過 stdio 執行的本機 npm 套件 @usefillo/mcp。需要 OAuth 驗證。開通與發布工具意味著需要 Fillo 帳號與工作區。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Fillo,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.jacobfunch%2Fusefillo/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"fillo": {
"type": "http",
"url": "https://fillo.so/api/mcp"
}
}
}README
[Fillo — forms inside your product, with your UI.]
Website · Docs · Agents · Examples · Changelog
[@usefillo/react npm version] [@usefillo/mcp npm version] [MIT license]
Fillo SDKs
Fillo is headless form infrastructure. You build a form in the hosted editor or define it in code, then render it inside your own product with your UI — React, Vue, Svelte, Astro, or plain browser JavaScript — instead of dropping in an iframe. One shared schema drives the builder, the renderers, API validation, and the responses grid, so a form looks and behaves like part of your app.
Files go browser-direct into storage you own (Google Drive, Box, or an S3-compatible bucket), resumable where the provider supports it. Responses land in a schema-aware grid with search, file downloads, a detail drawer, and CSV export, and can be delivered by signed webhooks, Google Sheets, Notion, Zapier, or email.
This repository holds the public SDK packages and the coding-agent skill. The product itself lives at fillo.so.
Packages
The canonical coding-agent skill (the same bundle the CLI installs) lives in
plugins/fillo/skills/build-with-fillo.
All packages are MIT licensed.
Quickstart
Install a renderer and drop a published form into your app. @usefillo/react
and @usefillo/dom both re-export the parts of @usefillo/core you need, so you
rarely install core directly.
Building with a coding agent
Fillo ships a provider-neutral Agent Skill that teaches your agent to build, embed, style, sync, and verify a Fillo form. Install it into a project:
In Claude Code or Codex, this repository is also a plugin marketplace. The plugin bundles the skill with the hosted Fillo MCP server:
Then point your agent at the setup flow. From a Build with AI handoff in the
product the CLI also prints a one-line npx @usefillo/cli agent bootstrap …
command that installs the skill and connects the live workspace in a single run.
See fillo.so/agents for the full agent path and
fillo.so/docs for the reference.
Links
- Website — fillo.so
- Docs — fillo.so/docs
- Agents — fillo.so/agents
- Examples — fillo.so/examples
- Changelog — fillo.so/changelog
About this repository
This repo is a read-only mirror of the public SDK packages. They are developed in a private monorepo and mirrored here on release, so the code you see is the same code published to npm. History here is disposable: the mirror is force-pushed by an automated job on every release, so don't fork from a specific commit expecting it to stay put — depend on the npm packages instead.
Issues and questions are welcome here — see CONTRIBUTING.md. Pull requests against package code can't be merged directly, since the source lives upstream; open an issue and we'll bring the fix through the private repo.
Note on the account name. This mirror currently lives at
github.com/jacobfunch/usefillowhile theusefilloGitHub organization is being claimed. Once it is, the repo will be transferred to the org; GitHub keeps the old path redirecting, so existing links and clones keep working.
來源:README.md,提交 bdcb97f
工具
0版本歷史
9- v0.11.2最新Oct 10, 2026
- v0.11.1Oct 10, 2026
- v0.11.0Oct 9, 2026
- v0.10.0Oct 4, 2026
- v0.9.0Sep 29, 2026
- v0.8.2Sep 27, 2026
- v0.8.0Sep 27, 2026
- v0.7.1Sep 23, 2026
- v0.3.1Sep 16, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分