Getting Started
ProofKit AI path from install through deploy, editing source, and redeploying updates.
This page is the overview for the ProofKit v2 happy path. Use it to understand the sequence: install ProofKit and connect MCP, explore your FileMaker file with your agent, build a Web Viewer app, deploy it into FileMaker, then keep working in your source project and redeploy when ready.
Each step below maps to one guide: install and connect (single walkthrough), explore, build, deploy, and editing after deploy — with detailed instructions and companion videos where available.
Before you start
Ensure you have the following prerequisites installed on your computer before installing ProofKit.
- FileMaker Pro (client for Mac or Windows)
- MCP-compatible coding agent (e.g. Cursor, Claude Desktop, Codex, etc.)
- Node.js (a supported LTS release, such as 22.x, 24.x, or 26.x)
- pnpm (version 11 is recommended; it is currently the most secure package manager option)
- Git (source control tool for managing the web code your agent will produce)
If you are using a chat-first tool such as Claude Desktop or ChatGPT, you can still use ProofKit to explore FileMaker metadata and data. Building Web Viewer apps requires a coding agent that can work in a project folder. See Chat Mode vs Code Mode for the difference.
See Technical Requirements for the full support matrix.
Setup
Install ProofKit, connect MCP, and verify your file.
Run the installer and add-on, run Connect to MCP in FileMaker Pro, keep the connector Web Viewer open in Browse mode, and ask your agent to confirm it sees your open file.
Continue with Install and Connect (covers install through verification).
Explore your file in chat mode.
Ask your agent about tables, layouts, fields, relationships, and data. This proves the connection is useful before you ask it to build anything. For a deeper explanation of exploration versus app development, see Chat Mode vs Code Mode.
Continue with Explore Your File.
Build a Web Viewer project.
Scaffold a project, run a local preview, ask your agent to build a real screen, and let the agent iterate with type checks and browser feedback.
Continue with Build a Web Viewer App.
Deploy into FileMaker.
Bundle the app, deploy it into your FileMaker file, and verify it runs inside the Web Viewer layout.
Continue with Deploy to FileMaker.
Edit source and redeploy.
Iterate on your project on disk — that is where your React and TypeScript source lives — then build and redeploy the bundle stored in FileMaker whenever you want users to pick up changes.
Continue with Edit your app.
What to read next
- Install and Connect covers installer, MCP connection, and verification.
- Edit your app separates source projects from bundles stored in FileMaker.
- Agent Workflow explains the read, write, verify, and fix loop.
- Hybrid Apps explains the runtime model.
- FAQ answers common scope, cost, and platform questions.