Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Fillo MCP server — provision, scaffold, publish, and query forms from your coding agent.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://fillo.so/api/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"usefillo": {
"command": "npx",
"args": [
"-y",
"@usefillo/mcp"
]
}
}
}在终端中运行这条命令
claude mcp add --transport http usefillo https://fillo.so/api/mcpclaude mcp add usefillo -- npx -y @usefillo/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"usefillo": {
"url": "https://fillo.so/api/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"usefillo": {
"command": "npx",
"args": [
"-y",
"@usefillo/mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"usefillo": {
"type": "http",
"url": "https://fillo.so/api/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"usefillo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@usefillo/mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://fillo.so/api/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 jacobfunch 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.11.2)于27天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, dotnet-mcp
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Website · Docs · Agents · Examples · Changelog
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](https://fillo.so).
| Package | npm | What it is |
|---|---|---|
@usefillo/core | npm · packages/core | Framework-agnostic form schema, validation, conditional-logic engine, prefill, formatting, JS client, and the browser-direct upload protocol. Zero framework dependencies. |
@usefillo/react | npm · packages/react | Headless React renderer, hooks, upload UI, and an optional default stylesheet you can override or replace. |
@usefillo/dom | npm · packages/dom | Framework-neutral DOM renderer, custom element, and a standalone browser bundle for Vue, Svelte, Astro, and vanilla apps. |
@usefillo/cli | npm · packages/cli | fillo — start a workspace, stage and publish forms, and install the Agent Skill from your terminal. |
@usefillo/mcp | npm · packages/mcp | MCP server — provision, scaffold, publish, and query forms from a coding agent. |
The canonical coding-agent skill (the same bundle the CLI installs) lives in plugins/fillo/skills/build-with-fillo. All packages are MIT licensed.
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.
// React / Next.js
import { FilloForm } from "@usefillo/react"; import "@usefillo/react/styles.css"; // optional default theme — or bring your own
confetti()} />
// Vue, Svelte, Astro, or plain browser JavaScript
import { createClient, defineForm, renderForm } from "@usefillo/dom"; import "@usefillo/dom/styles.css";
const client = createClient({ key: "pk_live_…" }); const form = defineForm({ id: "cust-feedback", pages: [{ id: "p1", blocks: [ { id: "email", kind: "email", label: "Work email", required: true }, { id: "message", kind: "long_text", label: "What should we know?" }, ] }], });
renderForm("#fillo-form", { form, client, onSubmitted: (id) => console.log(id) });
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:
npx @usefillo/cli@latest skill install
In Claude Code or Codex, this repository is also a plugin marketplace. The plugin bundles the skill with the hosted Fillo MCP server:
/plugin marketplace add jacobfunch/usefillo
/plugin install fillo@fillo
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](https://fillo.so/agents) for the full agent path and [fillo.so/docs](https://fillo.so/docs) for the reference.
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.