FormBridge

Mixed-mode agent-human form submission infrastructure. AI agents fill what they know, humans complete the rest — with full field-level attribution, approval workflows, and webhook delivery.

The Problem

AI agents can gather most of the data for a form — but some fields need a human: signatures, file uploads, identity verification, subjective preferences. Existing form tools force you to choose: fully automated or fully manual. Nothing handles the handoff.

How FormBridge Works

Agent                          FormBridge                        Human
  │                               │                                │
  ├─ POST /submissions ──────────►│  Creates draft, returns         │
  │  (fills known fields)         │  resumeToken + handoff URL      │
  │                               │                                │
  │                               │◄──── Opens link ────────────────┤
  │                               │  Pre-filled form with           │
  │                               │  attribution badges             │
  │                               │                                │
  │                               │◄──── Fills remaining fields ────┤
  │                               │◄──── Submits ──────────────────┤
  │                               │                                │
  │  ◄── Webhook delivery ───────┤  Validated, approved,           │
  │      (HMAC-signed)            │  delivered to destination       │

1. Agent creates a submission and fills fields it knows
2. FormBridge generates a secure resume URL with a rotating token
3. Human opens the link — sees pre-filled fields with "filled by agent" badges
4. Human completes remaining fields, uploads files, submits
5. Submission flows through validation → optional approval gates → webhook delivery
6. Every field tracks who filled it (agent, human, or system) and when

Packages

| Package | npm | Description | |---------|-----|-------------| | @agentkitai/formbridge-mcp-server | — | Core server — HTTP API, MCP tools, submission lifecycle, storage backends (main package) | | @agentkitai/formbridge-create | | CLI scaffolding tool (npx @agentkitai/formbridge-create) | | @agentkitai/formbridge-form-renderer | | React components and hooks for rendering forms and resuming agent-started submissions | | @agentkitai/formbridge-schema-normalizer | | Converts Zod, JSON Schema, and OpenAPI specs into a unified IntakeSchema IR | | @agentkitai/formbridge-shared | | Shared utilities across packages | | @agentkitai/formbridge-templates | | Ready-made intake templates (vendor onboarding, IT access, customer intake, expense report, bug report) | | @agentkitai/formbridge-admin-dashboard | — | React SPA for managing intakes, reviewing submissions, and configuring approvals |

Quick Start

Installation

The core server package (@agentkitai/formbridge-mcp-server) is not yet published to npm. Install it from source:

git clone https://github.com/agentkitai/formbridge.git
cd formbridge
npm install
npm run build

The companion packages (@agentkitai/formbridge-create, @agentkitai/formbridge-form-renderer, @agentkitai/formbridge-schema-normalizer, @agentkitai/formbridge-shared, @agentkitai/formbridge-templates) are published and can be installed directly from npm.

Option 1: HTTP API Server

import { createFormBridgeApp } from '@agentkitai/formbridge-mcp-server';
import { serve } from '@hono/node-server';

const app = createFormBridgeApp({
  intakes: [{
    id: 'contact-form',
    version: '1.0.0',
    name: 'Contact Form',
    schema: {
      type: 'object',
      properties: {
        name:    { type: 'string', title: 'Full Name' },
        email:   { type: 'string', format: 'email', title: 'Email' },
        message: { type: 'string', title: 'Message' },
      },
      required: ['name', 'email', 'message'],
    },
    destination: {
      type: 'webhook',
      name: 'Contact API',
      config: { url: 'https://api.example.com/contacts', method: 'POST' },
    },
  }],
});

serve({ fetch: app.fetch, port: 3000 });
console.log('FormBridge running on http://localhost:3000');

Full submission lifecycle:

# 1. Agent creates a submission with known fields
curl -X POST http://localhost:3000/intake/contact-form/submissions \
  -H 'Content-Type: application/json' \
  -d '{
    "actor": { "kind": "agent", "id": "gpt-4" },
    "idempotencyKey": "req_abc123",
    "initialFields": { "name": "John Doe", "email": "[email protected]" }
  }'
# → { ok: true, submissionId: "sub_...", resumeToken: "rtok_...", state: "draft" }

# 2. Human completes remaining fields via resume token
curl -X PATCH http://localhost:3000/intake/contact-form/submissions/sub_.../fields \
  -H 'Content-Type: application/json' \
  -d '{
    "resumeToken": "rtok_...",
    "actor": { "kind": "human", "id": "user-1" },
    "fields": { "message": "I'd like to learn more about your product." }
  }'

# 3. Submit the completed form
curl -X POST http://localhost:3000/intake/contact-form/submissions/sub_.../submit \
  -H 'Content-Type: application/json' \
  -d '{
    "resumeToken": "rtok_...",
    "actor": { "kind": "human", "id": "user-1" }
  }'
# → Triggers validation, approval (if configured), and webhook delivery

Option 2: MCP Server (for AI agents)

import { FormBridgeMCPServer } from '@agentkitai/formbridge-mcp-server';
import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
import { z } from 'zod';

const server = new FormBridgeMCPServer({
  name: 'my-formbridge',
  version: '1.0.0',
});

server.registerIntake({
  id: 'vendor_onboarding',
  version: '1.0.0',
  name: 'Vendor Onboarding',
  description: 'Register new vendors',
  schema: z.object({
    companyName: z.string().describe('Legal company name'),
    taxId:       z.string().describe('Tax identification number'),
    contact:     z.string().email().describe('Primary contact email'),
    w9Upload:    z.string().optional().describe('W-9 form upload (human-only)'),
  }),
  destination: {
    type: 'webhook',
    name: 'Vendor System',
    config: { url: 'https://api.example.com/vendors', method: 'POST' },
  },
});

// Each intake auto-generates 4 MCP tools:
//   vendor_onboarding__create   — Start a new submission
//   vendor_onboarding__set      — Update fields
//   vendor_onboarding__validate — Check completeness
//   vendor_onboarding__submit   — Submit for processing

const transport = new StdioServerTransport();
await server.getServer().connect(transport);

Option 3: React Form Renderer

import { FormBridgeForm, ResumeFormPage } from '@agentkitai/formbridge-form-renderer';

// Standalone form
function ContactPage() {
  return (
    <FormBridgeForm
      schema={contactSchema}
      endpoint="http://localhost:3000"
      actor={{ kind: 'human', id: 'user-1' }}
      onSuccess={(data, submissionId) => {
        console.log('Submitted:', submissionId);
      }}
    />
  );
}

// Resume an agent-started form (pre-filled fields + attribution badges)
function ResumePage() {
  const token = new URLSearchParams(location.search).get('token');
  return (
    <ResumeFormPage
      resumeToken={token}
      endpoint="http://localhost:3000"
    />
  );
}

Option 4: CLI Scaffolding

# Interactive — walks you through setup
npx @agentkitai/formbridge-create

# Non-interactive
npx @agentkitai/formbridge-create --name my-intake --schema zod --interface http,mcp

Features

Core

• Submission State Machine — draft → in_progress → submitted → finalized with configurable transitions
• Field Attribution — Every field tracks which actor (agent, human, system) set it and when
• Resume Tokens — Secure, rotating tokens for handoff URLs (rotated on every state change)
• Idempotent Submissions — Duplicate requests with the same key return the existing submission
• Schema Normalization — Accept Zod schemas, JSON Schema, or OpenAPI specs as input

Collaboration

• Mixed-Mode Forms — Agents fill what they can, humans complete the rest
• Conditional Fields — Show/hide fields based on other field values (dynamic schema)
• Multi-Step Wizard — Progressive disclosure with step indicators and navigation
• File Upload Protocol — Signed URL negotiation for secure file handling (S3-compatible)

Production

• Approval Gates — Configurable review workflows that pause submissions until approved/rejected
• Webhook Delivery — HMAC-signed payloads with exponential backoff and delivery tracking
• Event Stream — Append-only audit trail for every state change, field update, and action
• Auth & RBAC — API key auth, OAuth provider, role-based access control, rate limiting
• Multi-Tenancy — Tenant isolation with configurable storage and access boundaries
• Pluggable Storage — In-memory (dev), SQLite (single-server), PostgreSQL (multi-replica HA), S3 (file uploads)

Developer Experience

• MCP Server — Auto-generates MCP tools from intake definitions for AI agent integration
• Admin Dashboard — React SPA for managing intakes, reviewing submissions, analytics
• CLI Scaffolding — npx @agentkitai/formbridge-create generates a ready-to-run project
• 5 Starter Templates — Vendor onboarding, IT access request, customer intake, expense report, bug report
• VitePress Docs — API reference, guides, walkthroughs, and concept docs
• CI/CD — GitHub Actions for lint, typecheck, and tests on Node 18/20/22

API Reference

Endpoints

| Method | Path | Description | |--------|------|-------------| | GET | /health | Health check | | GET | /intake/:id/schema | Get intake schema | | POST | /intake/:id/submissions | Create submission | | GET | /intake/:id/submissions/:subId | Get submission | | PATCH | /intake/:id/submissions/:subId | Update fields | | POST | /intake/:id/submissions/:subId/submit | Submit | | GET | /submissions/:subId/events | Get event stream | | POST | /submissions/:subId/approve | Approve submission | | POST | /submissions/:subId/reject | Reject submission | | POST | /intake/:id/submissions/:subId/uploads | Request file upload URL | | POST | /intake/:id/submissions/:subId/uploads/:uploadId/confirm | Confirm file upload | | GET | /submissions/:subId/deliveries | List webhook deliveries for a submission | | GET | /webhooks/deliveries/:deliveryId | Get a single webhook delivery | | GET | /analytics/summary | Submission analytics summary | | GET | /analytics/volume | Submission volume over time | | GET | /analytics/funnel | Submission funnel by state | | GET | /analytics/intakes | Per-intake metrics |

Submission States

draft → in_progress → submitted → finalized
          │  ↘ awaiting_upload
          ↘ needs_review → approved → submitted/finalized
                        ↘ rejected

• draft — Newly created, being filled by agent and/or human
• in_progress — Fields are being set
• awaiting_upload — Waiting for a file upload to complete
• submitted — All required fields complete, pending review (or auto-approved)
• needs_review — Paused at an approval gate awaiting a reviewer decision
• approved — Passed approval gates
• rejected — Rejected by reviewer (terminal)
• finalized — Completed and delivered to destination (terminal)
• cancelled / expired — Terminal states for cancelled or TTL-expired submissions

Storage Backends

FormBridge supports multiple storage backends, selected via the FORMBRIDGE_STORAGE environment variable.

| Backend | Value | Use Case | Dependency | |---------|-------|----------|------------| | In-Memory | memory (default) | Development, testing | None | | SQLite | sqlite | Single-server production | better-sqlite3 | | PostgreSQL | postgres | Multi-replica HA deployments | pg |

PostgreSQL Configuration

# Required
export FORMBRIDGE_STORAGE=postgres
export DATABASE_URL=postgresql://user:password@host:5432/formbridge

# Optional: install pg driver
npm install pg

import { PostgresStorage } from '@agentkitai/formbridge-mcp-server';

const storage = new PostgresStorage({
  connectionString: process.env.DATABASE_URL!,
  maxConnections: 20,        // default: 10
  idleTimeoutMillis: 30000,  // default: 30000
});
await storage.initialize(); // runs migrations automatically

// Or use the factory:
import { createStorageFromEnv } from '@agentkitai/formbridge-mcp-server';
const storage = await createStorageFromEnv(); // reads FORMBRIDGE_STORAGE + DATABASE_URL

The PostgreSQL schema uses proper Postgres types: UUID for IDs, JSONB for structured data, and TIMESTAMPTZ for timestamps. The migration file is at migrations/001_init.sql.

Architecture

┌──────────────────────────────────────────────────────────┐
│                     FormBridge Core                       │
│                                                          │
│  ┌─────────────┐  ┌──────────────┐  ┌────────────────┐  │
│  │   Intake     │  │  Submission  │  │   Approval     │  │
│  │  Registry    │  │   Manager    │  │   Manager      │  │
│  └─────────────┘  └──────────────┘  └────────────────┘  │
│  ┌─────────────┐  ┌──────────────┐  ┌────────────────┐  │
│  │   Event      │  │   Webhook    │  │   Condition    │  │
│  │   Store      │  │   Manager    │  │   Evaluator    │  │
│  └─────────────┘  └──────────────┘  └────────────────┘  │
│                                                          │
│  ┌─────────────────────────────────────────────────────┐ │
│  │              Storage Layer                           │ │
│  │  Memory (dev) │ SQLite (prod) │ S3 (file uploads)   │ │
│  └─────────────────────────────────────────────────────┘ │
│                                                          │
│  ┌──────────────────┐  ┌──────────────────────────────┐  │
│  │   HTTP API        │  │   MCP Server                 │  │
│  │   (Hono)          │  │   (Stdio + SSE transports)   │  │
│  └──────────────────┘  └──────────────────────────────┘  │
│                                                          │
│  ┌──────────────────┐  ┌──────────────────────────────┐  │
│  │   Auth / RBAC     │  │   Rate Limiting              │  │
│  │   Multi-tenancy   │  │   CORS                       │  │
│  └──────────────────┘  └──────────────────────────────┘  │
└──────────────────────────────────────────────────────────┘

┌────────────────────┐  ┌────────────────────────────────┐
│  React Form        │  │  Admin Dashboard               │
│  Renderer          │  │  (React SPA)                   │
└────────────────────┘  └────────────────────────────────┘

┌────────────────────┐  ┌────────────────────────────────┐
│  CLI Scaffolding   │  │  Schema Normalizer             │
│  (create-formbridge)│  │  (Zod/JSONSchema/OpenAPI → IR) │
└────────────────────┘  └────────────────────────────────┘

Project Structure

src/
  auth/           # API key auth, OAuth, RBAC, rate limiting, tenant isolation
  core/           # Business logic — submission manager, approval gates, events,
                  #   state machine, condition evaluator, webhook delivery
  mcp/            # MCP server, tool generator, stdio + SSE transports
  middleware/     # Hono middleware (CORS, error handling)
  routes/         # HTTP route handlers (submissions, approvals, uploads, events,
                  #   webhooks, analytics, health)
  storage/        # Storage backends (memory, SQLite, S3) + migration utility
  types/          # TypeScript types and intake contract spec

packages/
  admin-dashboard/    # React SPA — intake management, submission review, analytics
  create-formbridge/  # CLI tool — interactive + non-interactive project scaffolding
  form-renderer/      # React components — FormBridgeForm, ResumeFormPage, WizardForm
  schema-normalizer/  # Converts Zod, JSON Schema, OpenAPI → unified IntakeSchema IR
  shared/             # Shared utilities across packages
  templates/          # 5 starter templates with full schema definitions
  demo/               # Demo app with sample intakes and pre-configured workflows

docs/               # VitePress documentation site
tests/              # 1,427 tests across 59 files
.github/workflows/  # CI (lint + typecheck + tests on Node 18/20/22) + release

Development

# Install dependencies
npm install

# Run all 1,427 tests
npm run test:run

# Watch mode
npm test

# Type checking (zero errors)
npm run typecheck

# Lint (ESLint flat config v9)
npm run lint

# Build
npm run build

# Run the demo app
cd packages/demo && npm run dev

Testing

The test suite covers:

• Core logic — Submission lifecycle, state machine transitions, approval workflows, field attribution
• API endpoints — Full HTTP request/response testing for all routes
• MCP server — Tool generation, server initialization, transport handling
• Storage backends — Memory, SQLite, and S3 storage with edge cases
• CLI scaffolding — End-to-end CLI tests (interactive + non-interactive)
• Schema normalization — Zod, JSON Schema, and OpenAPI conversion
• Condition evaluation — Dynamic field visibility rules
• Webhook delivery — HMAC signing, retry logic, delivery tracking

1,427 tests passing across 59 test files

(Two upload-path tests assert POSIX / separators and fail on Windows; they pass on Linux/macOS, which is what CI runs.)

Roadmap

• [x] npm package publishing (5 packages live on npm)
• [x] PostgreSQL storage backend
• [ ] Real-time collaboration (WebSocket field locking)
• [ ] Email notifications for pending approvals
• [ ] Form analytics dashboard with charts
• [ ] Hosted cloud version

Contributing

Contributions welcome! Please open an issue first to discuss what you'd like to change.

git clone https://github.com/agentkitai/formbridge.git
cd formbridge
npm install
npm run test:run   # All tests pass
npm run typecheck  # Zero errors
npm run lint       # Clean

🧰 AgentKit Ecosystem

| Project | Description | | |---------|-------------|-| | AgentLens | Observability & audit trail for AI agents | | | Lore | Cross-agent memory and lesson sharing | | | AgentGate | Human-in-the-loop approval gateway | | | FormBridge | Agent-human mixed-mode forms | ⬅️ you are here | | AgentEval | Testing & evaluation framework | | | agentkit-cli | Unified CLI orchestrator | |

License

MIT © 2026 Amit Paz