FileMaker Data API MCP Server
Provides tools for interacting with FileMaker databases via the FileMaker Data API, enabling AI agents to query, manage records, execute scripts, and introspect database schemas.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FileMaker Data API MCP Server Show me the first 10 records from the Orders layout"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FileMaker Data API MCP Server
A Model Context Protocol (MCP) server that provides AI agents with direct access to FileMaker databases through the FileMaker Data API. Compatible with Claude Desktop, Claude Code Console, Windsurf, Cursor, Cline, and other MCP-enabled AI assistants.
What It Does
This MCP server acts as a bridge between AI agents and FileMaker databases, enabling natural language interactions with your FileMaker data and database structure:
Data Interaction
Query databases - Retrieve, search, and analyze FileMaker records
Manage records - Create, update, delete, and duplicate records through conversation
Execute scripts - Run FileMaker scripts with parameters
Upload files - Add files to container fields (including repetitions)
Set global fields - Manage FileMaker global fields programmatically
Multi-database support - Switch between different FileMaker databases dynamically
Database Introspection
Discover structure - AI agents can introspect database schemas, layouts, and field definitions
Understand relationships - Access portal and related table information
Architect solutions - Enable AI to design and implement FileMaker applications through natural language
Metadata access - Get complete information about layouts, fields, value lists, and scripts
This introspection capability allows AI agents to understand your database architecture and help you build, modify, and optimize FileMaker solutions through simple conversation.
Related MCP server: MCP-Claude-FileMaker
Quick Start
Installation
npm install -g filemaker-data-api-mcpSetup
# Add your FileMaker connection
filemaker-mcp config add-connection production \
--server 192.168.0.24 \
--database Sales \
--user admin \
--password your_password
# Set as default
filemaker-mcp config set-default productionConfigure Your AI Agent
Claude Desktop
Edit your configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"filemaker": {
"command": "filemaker-mcp",
"args": ["start"]
}
}
}Windsurf / Cursor / Cline
Add to your MCP settings configuration:
{
"mcpServers": {
"filemaker": {
"command": "filemaker-mcp",
"args": ["start"]
}
}
}Restart your AI agent and you're ready!
Features
Connection Management
✅ Multiple connections - Store and switch between different FileMaker databases
✅ Dynamic switching - Change databases during conversations
✅ Inline credentials - Connect with ad-hoc credentials without pre-configuration
✅ Secure storage - Credentials stored with restricted file permissions
Data Operations
✅ Authentication - Login, logout, session validation
✅ Records - Create, read, update, delete, duplicate, find
✅ Metadata - Access database, layout, and script information
✅ Container fields - Upload files (including repetitions)
✅ Global fields - Set global field values
✅ Scripts - Execute FileMaker scripts with parameters
✅ Portal data - Access related records through portals
Network Transport
✅ stdio - Local use with Claude Desktop (default)
✅ HTTP/HTTPS - Network deployment for remote access
Usage Examples
Example 1: Query Your Database
You ask:
"Show me all contacts from the production database"The AI agent automatically connects and retrieves the data.
Example 2: Database Introspection
You ask:
"What is the structure of the Contacts layout? Show me all fields and their types."The AI agent introspects the database schema and provides detailed field information.
Example 3: Switch Between Databases
You ask:
"Compare sales records from production and staging databases"The AI agent switches between connections and compares the data.
Example 4: Create Records
You ask:
"Add a new contact: John Smith, john@example.com, 555-1234"The AI agent creates the record with the provided information.
Example 5: Ad-hoc Connection
You ask:
"Connect to 192.168.0.26, database TestDB, user admin, password test123. Show all records."The AI agent connects with inline credentials and queries the database.
Example 6: Solution Architecture
You ask:
"Design a customer management system with contacts, orders, and products. Create the layouts and suggest field definitions."The AI agent uses database introspection to understand your current structure and helps architect the solution.
Configuration
CLI Commands
# Initial setup
filemaker-mcp setup
# Connection management
filemaker-mcp config add-connection <name> [options]
filemaker-mcp config remove-connection <name>
filemaker-mcp config list-connections
filemaker-mcp config set-default <name>
filemaker-mcp config show
# Start server
filemaker-mcp start
# Configure Claude Desktop
filemaker-mcp configure-claudeEnvironment Variables
You can also configure via environment variables in the Claude Desktop config:
{
"mcpServers": {
"filemaker": {
"command": "filemaker-mcp",
"args": ["start"],
"env": {
"FM_SERVER": "192.168.0.24",
"FM_DATABASE": "Sales",
"FM_USER": "admin",
"FM_PASSWORD": "your_password",
"FM_VERSION": "vLatest"
}
}
}
}Configuration Priority
Environment variables (highest) - defined in MCP config
CLI-configured connections - stored in
~/.filemaker-mcp/config.jsonInline credentials (lowest) - passed dynamically via tool parameters
Available Tools
The MCP server provides 28 tools for interacting with FileMaker:
Authentication (3 tools)
fm_login- Authenticate with FileMaker Serverfm_logout- End sessionfm_validate_session- Check session validity
Metadata (5 tools)
fm_get_product_info- Get FileMaker Server infofm_get_databases- List available databasesfm_get_layouts- Get layouts for a databasefm_get_scripts- Get scripts for a databasefm_get_layout_metadata- Get layout field metadata
Records (7 tools)
fm_get_records- Get records with paginationfm_get_record_by_id- Get single recordfm_create_record- Create new recordfm_edit_record- Update existing recordfm_delete_record- Delete recordfm_duplicate_record- Duplicate recordfm_find_records- Search records
Container Fields (2 tools)
fm_upload_to_container- Upload file to container fieldfm_upload_to_container_repetition- Upload to repeating container field
Global Fields (1 tool)
fm_set_global_fields- Set global field values
Scripts (1 tool)
fm_execute_script- Execute FileMaker script
Configuration Tools (5 tools)
fm_config_add_connection- Add predefined connectionfm_config_remove_connection- Remove connectionfm_config_list_connections- List all configured connectionsfm_config_get_connection- Get connection details (password masked)fm_config_set_default_connection- Set default connection
Connection Tools (4 tools)
fm_set_connection- Switch to predefined connectionfm_connect- Connect with inline credentials (one-time)fm_list_connections- List available connectionsfm_get_current_connection- Show current connection details
Prerequisites
Node.js v18 or higher
FileMaker Server with Data API enabled
Valid FileMaker credentials with appropriate privileges
Documentation
Getting Started Guide - Detailed setup instructions
User Guide - Complete usage documentation
Token Lifecycle Management - Token caching, refresh, and error recovery
Deployment Guide - Production deployment instructions
API Reference - All tools documented
Development Guide - For contributors
Security
Credentials stored in
~/.filemaker-mcp/config.jsonwith restricted permissions (0o600)Passwords masked in list/show commands
Never share your config file or commit it to version control
Use strong passwords for FileMaker Server accounts
For production, consider using environment variables
Troubleshooting
Connection Issues
# List your connections
filemaker-mcp config list-connections
# Verify connection details
filemaker-mcp config showClaude Desktop Not Responding
Verify installation:
filemaker-mcp config list-connectionsRebuild if needed:
npm install -g filemaker-data-api-mcp@latestRestart Claude Desktop
Authentication Failed
Verify FileMaker Server is running and accessible
Check username and password are correct
Ensure Data API is enabled on FileMaker Server
Verify user has proper privileges
Development
Local Development
# Clone repository (update URL after publishing)
git clone https://github.com/yourusername/filemaker-data-api-mcp.git
cd filemaker-data-api-mcp
# Install dependencies
npm install
# Build
npm run build
# Run tests
npm test
# Start in development mode
npm run devUse as Library
import { ConnectionManager } from 'filemaker-data-api-mcp';
const manager = new ConnectionManager();
manager.addConnection('mydb', {
server: '192.168.0.24',
database: 'Sales',
user: 'admin',
password: 'xxx',
version: 'vLatest'
});Contributing
Contributions are welcome! See the Development Guide for implementation details and the Testing Guide for testing guidelines.
License
MIT License - see LICENSE file for details
Resources
Support
Documentation: docs/
Changelog: CHANGELOG.md
Issues: GitHub Issues (update URL after publishing)
Made with ❤️ for the FileMaker and AI community
Available Tools
28 toolsfm_config_add_connectionB
Add a new predefined FileMaker database connection to the configuration
Inputs: name (required), user (required), server (required), database (required), +2 more.
fm_config_get_connectionB
Get details of a specific connection (password is masked for security)
Inputs: name (required).
fm_config_list_connectionsB
List all available predefined database connections
Inputs: no named parameters.
fm_config_remove_connectionB
Remove a predefined database connection from the configuration
Inputs: name (required).
fm_config_set_default_connectionA
Set the default connection to use when the server starts
Inputs: name (required).
fm_connectB
Connect to a FileMaker database with inline credentials (one-time connection)
Inputs: user (required), server (required), database (required), password (required), +1 more.
fm_create_recordB
Create a new record in a layout
Inputs: layout (required), fieldData (required), database.
fm_delete_recordC
Delete a record by its recordId
Inputs: layout (required), recordId (required), database.
fm_duplicate_recordC
Duplicate an existing record
Inputs: layout (required), recordId (required), database.
fm_edit_recordC
Edit an existing record
Inputs: layout (required), recordId (required), fieldData (required), database.
fm_execute_scriptB
Execute a FileMaker script from a specific layout
Inputs: layout (required), scriptName (required), database, scriptParameter.
fm_find_recordsC
Find records using a query. Query is an array of search criteria objects.
Inputs: query (required), layout (required), limit, offset, +1 more.
fm_get_current_connectionA
Get the currently active database connection details (password masked)
Inputs: no named parameters.
fm_get_databasesA
List all available databases on the FileMaker Server
Inputs: no named parameters.
fm_get_layout_metadataA
Get metadata for a specific layout including field definitions
Inputs: layout (required), database.
fm_get_layoutsB
Get all layouts for a database
Inputs: database.
fm_get_product_infoA
Get FileMaker Server product information including date/time formats
Inputs: no named parameters.
fm_get_record_by_idC
Get a single record by its recordId
Inputs: layout (required), recordId (required), database.
fm_get_recordsB
Get records from a layout with pagination
Inputs: layout (required), limit, offset, database.
fm_get_scriptsA
Get all scripts for a database
Inputs: database.
fm_list_connectionsB
List all available predefined database connections
Inputs: no named parameters.
fm_loginA
Authenticate with FileMaker Server and get a session token. Required before using most other tools. External database credentials can be configured via .env (FM_EXTERNAL_DATABASES) or passed as fmDataSource parameter.
Inputs: database, password, username, fmDataSource.
fm_logoutA
End the current FileMaker Server session
Inputs: no named parameters.
fm_set_connectionB
Switch to a predefined FileMaker database connection
Inputs: connectionName (required).
fm_set_global_fieldsC
Set global field values
Inputs: globalFields (required), database.
fm_upload_to_containerC
Upload a file to a container field
Inputs: layout (required), filePath (required), recordId (required), containerFieldName (required), +1 more.
fm_upload_to_container_repetitionB
Upload a file to a container field with repetition
Inputs: layout (required), filePath (required), recordId (required), repetition (required), +2 more.
fm_validate_sessionA
Check if the current session token is still valid
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 28 tools
Most tools have distinct purposes, but there is clear overlap: fm_list_connections and fm_config_list_connections have identical descriptions, causing ambiguity. Also, fm_set_connection and fm_connect serve similar roles (switching connections) with subtle differences. These duplicates reduce clarity.
All tools follow a consistent 'fm_verb_noun' pattern. Verbs like config_add, get, create, edit, delete, find are used predictably. The prefix 'config_' for configuration tools adds internal consistency without breaking the pattern.
With 28 tools, the count is on the high side for an MCP server. While FileMaker has many operations, some tools like the two upload container tools could be merged. The number is borderline between 'slightly over' and 'too many' per the rubric.
The tool set covers the full lifecycle: configuration, session management, metadata retrieval, CRUD operations, finding, file uploads, global field setting, and script execution. There are no obvious gaps for typical FileMaker Data API usage.
Related MCP Connectors
Query and update Teable records, manage tables, and access the Teable API with AI agents.
Give AI agents access to form submissions — read, search, update, and process file attachments.
Store, query, and update structured data from any AI agent
Create AgentUI data apps: define tables, read and write records, and run programs on your data.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to connect to and interact with PostgreSQL, MySQL, SQLite, and MongoDB databases through natural language, supporting schema exploration, query execution, data export, and more.13MIT
- AlicenseBqualityDmaintenanceEnables Claude to interact with FileMaker databases through the FileMaker Data API, supporting multi-database connections, CRUD operations, script execution, and metadata discovery.1111MIT
- AlicenseBqualityDmaintenanceEnables AI agents to interact with local SQLite databases with full CRUD, schema introspection, foreign key relations, generated columns, and multi-format import/export (CSV, JSON, XLSX) through natural language.2610 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to query, analyze, and discover FileMaker database schemas via OData v4, with pandas-powered analytics for efficient data summaries.1310GPL 3.0