
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 分