Connect your AI assistant — Claude, ChatGPT, Copilot, and more — directly to Fulcrum. The AI Toolkit gives it the know-how; Fulcrum MCP gives it the tools to act on that knowledge. We recommend installing both.
What does "Labs" mean?
"Labs" means this is an early version, still in progress. We’re releasing it now so you can start using and shaping it, ahead of the full testing and polish a general-availability release gets. Expect some rough edges, and expect things to change as we iterate. Try it in a non-production environment first, and tell us what doesn’t work — see "Questions or feedback" below.
What’s the difference between the two?
Fulcrum AI Toolkit — the know-how. A library of skills that teaches your assistant Fulcrum’s best practices — the right field types, safe automation patterns, what to flag — so it uses Fulcrum MCP well, not just correctly. Works on its own, too: without a live connection it stops at a ready-to-implement schema and handoff instead of building live.
Fulcrum MCP — the connection. Lets your assistant build and manage things in your Fulcrum org: create and update forms, manage choice lists and webhooks, generate app extensions and report templates, and query your live data.
MCP alone still works, but your assistant is improvising. The Toolkit is what turns "technically possible" into "built the way we’d build it." Today they install as two separate steps — use both for the best results.
What can you do with it?
Build a new Fulcrum app from a plain-language description, with correctly configured fields, sections, and choice lists.
Update an existing app — add or change fields, adjust automation, rename elements.
Create and manage shared choice lists used across multiple apps.
Set up webhooks to send Fulcrum data to other systems.
Generate custom app extensions (rich, in-record UIs) from proven patterns — no hand-written code.
Build report templates and generate reports from your data.
Query your own Fulcrum records directly — read-only, safe to explore.
Get platform details right the first time — the Toolkit gives your assistant Fulcrum’s field types, automation functions, and safety checks, so it isn’t guessing.
Get started
Step 1 — Install the Fulcrum AI Toolkit. No credentials needed, and it’s useful right away in handoff mode. Do this first.
Claude Code
/plugin marketplace add https://github.com/fulcrumapp/fulcrum-ai-toolkit.git
/plugin install fulcrum-ai-toolkit@fulcrum-ai-toolkit
Claude Desktop chat and Cowork can’t install the Toolkit yet — that’s on us, not you. It needs account-level skill packaging support that isn’t there yet; we’ll update this article once it is.
ChatGPT
Custom GPT (recommended): ask us for a pre-built Fulcrum Builder GPT with the Toolkit’s skills built in and MCP configured as an action — tools and guidance in one place.
Or, Developer Mode: Settings → Connectors → paste the MCP server URL from Step 2 below. This gives ChatGPT the MCP tools without the Toolkit’s guidance.
GitHub Copilot
copilot plugin marketplace add fulcrumapp/fulcrum-ai-toolkit
copilot plugin install fulcrum-ai-toolkit@fulcrum-ai-toolkit
Copilot Chat (VS Code): paste the Toolkit’s GitHub URL into chat and ask Copilot to install it — it auto-detects the skills.
Other assistants (Cursor, Codex, Gemini / Antigravity, Hermes, and more)
npx skills@latest add https://github.com/fulcrumapp/fulcrum-ai-toolkit/tree/main/plugins/fulcrum-ai-toolkit/skills --skill '*'
Exact steps vary slightly by tool — see your assistant’s plugin or connector settings.
Step 2 — Connect Fulcrum MCP, for live building. This is what turns guidance into action. You’ll need an API token from your account settings, and your organization’s regional endpoint below. Authentication is by Bearer token only — OAuth sign-in isn’t supported yet.
Pick your region’s endpoint
Use the endpoint for your organization’s Fulcrum instance, not your physical location — there’s no automatic fallback between regions.
United States (default): https://mcp.fulcrumapp.com/mcp
Australia: https://mcp.fulcrumapp-au.com/mcp
Europe: https://mcp.fulcrumapp-eu.com/mcp
Canada: https://mcp.fulcrumapp-ca.com/mcp
Paste this into your assistant’s MCP or connector settings. Replace the "url" value with your region’s endpoint from the table above if you’re not on the US default, and swap in your token:
{
"mcpServers": {
"fulcrum-app": {
"url": "https://mcp.fulcrumapp.com/mcp",
"headers": { "Authorization": "Bearer YOUR_FULCRUM_API_TOKEN" }
}
}
}Using Claude Code? Keep the token out of files that might get committed — merge this into your project’s .mcp.json instead, and set FULCRUM_MCP_URL to your region’s endpoint from the table above (not just the US default shown here) and FULCRUM_API_TOKEN to your token, as environment variables rather than pasting either literally:
{
"mcpServers": {
"fulcrum-app": {
"type": "http",
"url": "${FULCRUM_MCP_URL}",
"headers": { "Authorization": "Bearer ${FULCRUM_API_TOKEN}" }
}
}
}
Two easy mistakes when pasting your token
Keep the word "Bearer" in front of your token in the Authorization header — don’t replace the whole value with just the token.
Copy carefully — a stray line break picked up in the copy-paste will break the token, and the failure may not be obvious.
A couple of rough edges to expect
If your assistant connects but nothing seems to work, double-check your token first — an invalid token doesn’t always show up as a clean connection error. Sometimes the connection succeeds and the failure only shows up on the first thing you try.
Right after connecting, you might see a one-time error that clears up if you just try again. That’s a known early rough edge, not something wrong on your end.
What’s under the hood
Fulcrum MCP currently gives your assistant 56 tools across 17 categories — 53 for building and managing your Fulcrum apps (forms, choice lists, webhooks, extensions, report templates, and more) plus 3 for querying your live data. The AI Toolkit ships 16 skills today, covering the full build lifecycle: running discovery conversations, choosing field types and structure, writing safe automation, flagging gaps like missing safety fields, and querying data the right way.
Full tool-by-tool and skill-by-skill reference lives in the repo, not duplicated here, so it stays current with the code: github.com/fulcrumapp/fulcrum-ai-toolkit
Questions or feedback
Fulcrum MCP and the AI Toolkit are new and under active development. If something doesn’t work as expected, or you’d like to see a capability that isn’t listed here, email [email protected] — your feedback directly shapes what we build next.