Connect FileMaker to Claude
Expose your FileMaker data to Claude Desktop and Claude.ai through an MCP-compatible connection instead of copying records into chat or exporting spreadsheets.
Ask Claude Questions About Your FileMaker Data
FM Dojo connects FileMaker databases to Claude, Cursor, and other MCP-compatible AI tools. Ask questions in plain English, inspect live records, summarize operational data, and reason across databases without exports, custom API work, or putting credentials in local config files.
Claude DesktopClaude MobileCursorZedContinue.devLive FileMaker dataRevocable tokens
Instead of this
Exporting FileMaker data to CSV
Pasting records into AI chats
Building one-off Data API scripts
Putting credentials in local MCP config files
Do this
Ask your AI tool directly.
“Which open opportunities have had no activity in 30 days, and which customer records need follow-up first?”
See how easy it is to connect Claude to your FileMaker data
A quick walkthrough of setting up FM Dojo with Claude, so you can ask questions from Claude on desktop, web, or mobile.
What It Does
Secure AI Access for Real FileMaker Workflows
This is not a chatbot pasted onto FileMaker. It is a controlled data access layer that lets MCP-compatible AI tools work with your actual FileMaker solution.
Use Cursor, Zed, and other MCP tools
FM Dojo is not locked to one AI client. Use the same FileMaker access layer with modern MCP-compatible tools used by developers and technical teams.
Query live FileMaker data
Ask about customers, invoices, orders, inventory, tickets, or whatever your solution stores. The AI works against current FileMaker data, not stale exports.
Keep credentials out of config files
Claude, Cursor, and local MCP clients do not need your FileMaker username and password. FM Dojo uses generated tokens that can be revoked when access should end.
Understand your schema
The AI can work with your real layouts, tables, and fields, so questions can use the language of your FileMaker solution instead of generic placeholders.
Work across databases
Select multiple FileMaker databases when creating a token, then give Claude one connector URL that can reach all of them. Cursor, Zed, and other config-file tools can still use separate tokens when you want stricter scoping.
Why It Matters
FileMaker Teams Need AI That Can See the Actual System
Generic AI can explain FileMaker concepts. FM Dojo AI Data Access goes further: it lets your AI tool inspect the data that drives the business, while keeping access scoped through FM Dojo.
View Plans✓
Ask Claude which invoices are overdue and summarize the risk.
✓
Have Cursor inspect FileMaker records while helping you debug business logic.
✓
Compare customers, orders, tickets, or inventory across connected databases.
✓
Create plain-English reporting without building another dashboard first.
✓
Let business owners ask operational questions without learning SQL or Data API syntax.
Setup
From FileMaker to AI in Three Steps
1
Create a database token
Connect a FileMaker database in FM Dojo and generate a scoped token for that database.
2
Add it to your AI tool
Use the connector URL or generated MCP config with Claude, Cursor, Zed, Continue.dev, or another MCP-compatible client.
3
Ask business questions
Find records, summarize activity, inspect customer history, compare results, and reason over live FileMaker data.
Examples
Questions Your FileMaker Data Can Answer
Use natural language instead of building a report, writing SQL, or exporting data first.
Find records
“Show me all invoices with a balance over $500 that are more than 30 days overdue.”
Summarize data
“How many active customers do we have in California vs. Texas?”
Look up records
“What are the most recent 10 orders for Acme Corp?”
Cross-field logic
“Which products have inventory below their reorder point?”
Aggregate data
“What is the total revenue for each sales rep this quarter?”
Date logic
“Find all records where the follow-up date has passed and the status is still open.”
Access Control
Built for Teams That Care About Data Access
AI data access should not mean pasting credentials into desktop tools or spreading database passwords across developer machines. FM Dojo gives each database a revocable access path.
No FileMaker credentials in local AI config files.
One token can cover one database for strict scoping or several databases for Claude's single-connector workflow.
Access can be revoked without changing database passwords.
Your AI tool works through FM Dojo instead of direct credential sharing.
Access without chaos
Need help deciding what AI should be allowed to see?
Book consulting for a calm access plan: which databases, which accounts, which records, and how to keep the impressive demo from becoming a permission soup.
Unblock a lesson
Review your approach
Plan the next build
FAQ
Common Questions
Which AI tools does this work with?
FM Dojo works with MCP-compatible AI tools, including Claude Desktop, Claude.ai connectors, Cursor, Zed, Continue.dev, and other tools that support the Model Context Protocol.
Are my FileMaker credentials stored in Claude or Cursor?
No. Your AI tool receives a generated FM Dojo token, not your FileMaker username and password. Tokens can be revoked independently.
Can I connect more than one database?
Yes. A single FM Dojo AI Data Access token can include multiple FileMaker databases, so Claude can reach them through one custom connector URL. You can still create separate tokens when you want narrower access.
Does FM Dojo store my FileMaker records?
No. FM Dojo acts as a secure access layer. It forwards approved requests to your FileMaker Server and returns the result to your AI tool without storing record data as application content.
Stop exporting FileMaker data just to ask AI a question.
Connect FileMaker to Claude, Cursor, and MCP-compatible tools with scoped, revocable access.
View Plans