Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Fillo MCP server — provision, scaffold, publish, and query forms from your coding agent.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://fillo.so/api/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"usefillo": {
"command": "npx",
"args": [
"-y",
"@usefillo/mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http usefillo https://fillo.so/api/mcpclaude mcp add usefillo -- npx -y @usefillo/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"usefillo": {
"url": "https://fillo.so/api/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"usefillo": {
"command": "npx",
"args": [
"-y",
"@usefillo/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"usefillo": {
"type": "http",
"url": "https://fillo.so/api/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"usefillo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@usefillo/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://fillo.so/api/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account jacobfunch, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.11.2) reached the registry 27 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Recta
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.