Technical Requirements
What you need to build and run ProofKit v2 apps.
ProofKit v2 is designed for FileMaker developers using agentic coding tools to build Web Viewer apps.
FileMaker version
ProofKit v2 requires FileMaker 22 or greater.
Future ProofKit releases will track the next major FileMaker release cycle so ProofKit can take advantage of new platform capabilities as they become available.
Development machine
To build ProofKit apps, you need:
- FileMaker Pro with the target file open.
- Node.js LTS installed locally. Choose a release that is explicitly marked LTS. Today that means Node.js 22, Node.js 24, or Node.js 26.
- pnpm version 11 is recommended. It is currently the most secure package manager option.
- An MCP-compatible coding agent, such as Cursor, Claude Code, Codex, OpenCode, or another agent that supports MCP servers.
FileMaker Server is not required for the development loop. ProofKit can work against a local or hosted file as long as it is open in FileMaker Pro.
Node.js
ProofKit projects use Node.js for the local development tools that scaffold, build, preview, and deploy Web Viewer apps. Pick an LTS release rather than the newest "Current" release. Node's odd-numbered releases are short-lived, and not every even-numbered release is the right choice forever; use a version that nodejs.org marks as LTS.
If you are not already managing Node versions, the native installer from nodejs.org is the simplest option.
Download the LTS installer for macOS or Windows from nodejs.org/download. Choose Node.js 26 LTS when available, or Node.js 24 LTS or Node.js 22 LTS if your environment standardizes on one of those versions.
After installing, verify the version:
node -v
npm -vOn macOS, Homebrew is convenient if you already use it. Install a versioned LTS formula instead of the unversioned node formula, which may track a newer non-LTS release.
brew install node@24
node -vIf node is not found after installation, run brew info node@24 and follow Homebrew's PATH instructions.
Use a version manager if you switch between projects with different Node requirements.
nvm install --lts
nvm use --ltsfnm and Volta are good alternatives. The important part is pinning your project to an LTS line such as Node.js 26, Node.js 24, or Node.js 22.
pnpm
ProofKit projects use pnpm for workspace installs, scripts, and monorepo tooling. We recommend pnpm 11 because it is the fastest and most secure package manager available for the Node.js ecosystem.
- Learn more: pnpm.io
- Installation guide: pnpm installation docs
After installing, verify your version:
pnpm -vDeveloper background
You do not need to be a web developer to get started. Familiarity with React, TypeScript, a terminal, and Git will help, but the workflow is designed so the agent does much of the setup and implementation work.
Runtime environments
After a Web Viewer app is bundled and deployed into FileMaker, it can run in:
- FileMaker Pro on macOS and Windows.
- FileMaker Go on iOS and iPadOS.
- FileMaker WebDirect.
See Platform Notes for runtime caveats.
Out of scope for v2
ProofKit v2 enables agentic coding of Web Viewer apps. It does not currently enable agentic editing of:
- Scripts.
- Tables and fields.
- Layouts.
- Value lists.
- Other FileMaker schema or design elements.
Summary
| Requirement | Value |
|---|---|
| FileMaker version | FileMaker 22 or greater |
| Agent environment | Any MCP-compatible agent |
| Development requirements | FileMaker Pro and Node.js 22, 24, or 26 LTS |
| FileMaker Server | Not required for local development |
| Runtime platforms | FileMaker Pro, FileMaker Go, WebDirect |
| Agent writing scope | Web Viewer app code |