Fillo

io.github.jacobfunchPublished by GitHub account jacobfunchv0.11.2Updated Oct 24, 2026

Fillo MCP server — provision, scaffold, publish, and query forms from your coding agent.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Fillo's MCP server lets a coding agent provision, scaffold, publish and query headless forms hosted on fillo.so.

What you can do
Provision and set up a Fillo workspace and forms from the agent, including the Build with AI handoff flow that connects a live workspace in one run (per the README). Scaffold and publish forms so they can be rendered inside your own app with the Fillo SDKs. Query forms and their responses, which land in a schema-aware grid with search, downloads and CSV export. Build, embed, style, sync and verify a Fillo form alongside the provider-neutral Agent Skill.
When to use it
Useful when you are building a product with Fillo headless forms and want your coding agent to create, publish or inspect forms and responses without switching to the hosted editor. Less relevant if you do not use Fillo.
Requirements
A remote endpoint at fillo.so or the local npm package @usefillo/mcp over stdio. OAuth authentication is required. A Fillo account and workspace are implied by the provisioning and publish tools.
Before you install
OAuth grants the agent access to your Fillo workspace, and the tools can publish forms and query submitted responses, which may contain personal data. File uploads go browser-direct to storage you own (Google Drive, Box or an S3-compatible bucket), and responses can be forwarded to third parties such as Google Sheets, Notion, Zapier or email.

Installation

In SourceWeft

  1. Open Fillo in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.jacobfunch%2Fusefillo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "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

PackagenpmWhat it is
@usefillo/corenpm · packages/coreFramework-agnostic form schema, validation, conditional-logic engine, prefill, formatting, JS client, and the browser-direct upload protocol. Zero framework dependencies.
@usefillo/reactnpm · packages/reactHeadless React renderer, hooks, upload UI, and an optional default stylesheet you can override or replace.
@usefillo/domnpm · packages/domFramework-neutral DOM renderer, custom element, and a standalone browser bundle for Vue, Svelte, Astro, and vanilla apps.
@usefillo/clinpm · packages/clifillo — start a workspace, stage and publish forms, and install the Agent Skill from your terminal.
@usefillo/mcpnpm · packages/mcpMCP 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.

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.

tsx
// React / Next.jsimport { FilloForm } from "@usefillo/react";import "@usefillo/react/styles.css"; // optional default theme — or bring your own
<FilloForm formId="cust-feedback" onSubmitted={(responseId) => confetti()} />
ts
// Vue, Svelte, Astro, or plain browser JavaScriptimport { 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) });

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:

sh
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:

text
/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 for the full agent path and fillo.so/docs for the reference.

Links

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/usefillo while the usefillo GitHub 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.

Source: README.md at commit bdcb97f

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

9
  1. v0.11.2LatestOct 10, 2026
  2. v0.11.1Oct 10, 2026
  3. v0.11.0Oct 9, 2026
  4. v0.10.0Oct 4, 2026
  5. v0.9.0Sep 29, 2026
  6. v0.8.2Sep 27, 2026
  7. v0.8.0Sep 27, 2026
  8. v0.7.1Sep 23, 2026
  9. v0.3.1Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts