mcp-server-filemaker
An MCP server that provides AI assistants with direct access to FileMaker databases via OData v4 API, enabling CRUD operations, script execution, and schema introspection.
README
mcp-server-filemaker
MCP server that gives AI assistants direct access to FileMaker databases via OData v4 API.
Works with any MCP-compatible client: Claude Code, Claude Desktop, Cursor, Windsurf, Continue.dev, Zed, and others.
Runs on-premise — no cloud proxy, no Claris ID required.
MCP Client ──stdio──▶ MCP Server (Node.js) ──OData v4 / HTTPS──▶ FileMaker Server
Features
- 20 tools — CRUD, scripts, schema introspection, batch requests, test & validation
- OData v4 — direct table access (not layout-based like the Data API)
- Data API bridge — set global fields and run scripts with session context
- Tool restrictions — disable dangerous tools per database via
FM_DISABLED_TOOLS - Zero dependencies beyond the MCP SDK and Zod
Prerequisites
- FileMaker Server with OData access enabled (Admin Console → Connectors → OData)
- A dedicated API user with Extended Privilege
fmodata - For Data API tools (
fm_set_globals,fm_run_script_with_globals): alsofmrest - HTTPS with a valid certificate — self-signed certificates are not supported
Installation
git clone https://github.com/JoergKoester/mcp-server-filemaker.git
cd mcp-server-filemaker
npm install
npm run build
Configuration
Add the server to your MCP client config. For Claude Code and Claude Desktop, edit ~/.mcp.json:
{
"mcpServers": {
"filemaker": {
"command": "node",
"args": ["/absolute/path/to/mcp-server-filemaker/dist/index.js"],
"env": {
"FM_HOST": "https://your-filemaker-server.example.com",
"FM_DATABASE": "YourDatabase",
"FM_USERNAME": "api_user",
"FM_PASSWORD": "your_password",
"FM_ODATA_VERSION": "v4",
"FM_TIMEOUT_MS": "15000",
"FM_RETRY_COUNT": "2",
"FM_DISABLED_TOOLS": "",
"FM_DEBUG": "false"
}
}
}
}
Environment Variables
| Variable | Required | Description |
|---|---|---|
FM_HOST |
Yes | FileMaker Server URL with protocol, e.g. https://fms.example.com |
FM_DATABASE |
Yes | Database name |
FM_USERNAME |
Yes | API user (needs Extended Privilege fmodata) |
FM_PASSWORD |
Yes | Password |
FM_ODATA_VERSION |
No | OData version, default v4 |
FM_TIMEOUT_MS |
No | HTTP request timeout in milliseconds, default 15000 |
FM_RETRY_COUNT |
No | Retry attempts on transient failures (429/503), default 2 (set 0 to disable) |
FM_DISABLED_TOOLS |
No | Comma-separated tool names to disable |
FM_DEBUG |
No | true to log full tool arguments to stderr (may include record data) |
Multiple Databases
Run one server instance per database:
{
"mcpServers": {
"filemaker-app": {
"command": "node",
"args": ["/path/to/dist/index.js"],
"env": {
"FM_HOST": "https://fms.example.com",
"FM_DATABASE": "MyApp",
"FM_USERNAME": "api_user",
"FM_PASSWORD": "secret",
"FM_DISABLED_TOOLS": "fm_create_table,fm_add_field"
}
},
"filemaker-data": {
"command": "node",
"args": ["/path/to/dist/index.js"],
"env": {
"FM_HOST": "https://fms.example.com",
"FM_DATABASE": "MyData",
"FM_USERNAME": "api_user",
"FM_PASSWORD": "secret",
"FM_DISABLED_TOOLS": "fm_create_table,fm_add_field,fm_delete_record"
}
}
}
}
Tools
Structure & Metadata
| Tool | Description |
|---|---|
fm_get_service_document |
List all tables |
fm_get_metadata |
Full EDMX schema (fields, types, relationships) |
fm_introspect |
Tables overview or field details with native FM types |
Data Access
| Tool | Description |
|---|---|
fm_query |
Query records with $filter, $select, $top, $orderby, $expand, $count |
fm_get_record |
Single record by ROWID |
fm_create_record |
Create a new record |
fm_update_record |
Update record (PATCH) |
fm_delete_record |
Delete record by ROWID |
Scripts & Schema
| Tool | Description |
|---|---|
fm_run_script |
Execute a FileMaker script |
fm_create_table |
Create a new table |
fm_add_field |
Add a field (SQL-style types: VARCHAR(n), INT, NUMERIC, DATE, etc.) |
fm_batch |
Batch multiple OData requests in one HTTP call |
Data API (Session Context)
| Tool | Description |
|---|---|
fm_set_globals |
Set global fields (Login → PATCH /globals → Logout) |
fm_run_script_with_globals |
Set globals + run script in one session |
Test & Validation
| Tool | Description |
|---|---|
fm_create_test_record |
Create a tagged test record |
fm_cleanup_test_data |
Delete all records matching a test tag |
fm_assert_record |
Validate field values (PASS/FAIL with diff) |
fm_assert_count |
Assert record count for a query |
fm_run_script_and_assert |
Run script and check result code |
Tool Restrictions
Disable tools per database instance via FM_DISABLED_TOOLS:
FM_DISABLED_TOOLS=fm_create_table,fm_add_field,fm_delete_record
- Disabled tools are hidden from the tool list and blocked at execution (double protection)
- Server startup shows
Tools: 17/20and lists disabled tools - Recommended: always disable
fm_create_tableandfm_add_fieldon production databases
Architecture
4 files in src/:
| File | Responsibility |
|---|---|
index.ts |
Entry point, env config, STDIO transport, tool routing |
odata-client.ts |
HTTP client for all OData v4 requests (CRUD, scripts, schema, batch) |
data-api-client.ts |
HTTP client for FileMaker Data API (globals, session-scoped scripts) |
tools.ts |
MCP tool definitions (Zod schemas), handler logic, test tools |
The server is a thin proxy — no caching. Each OData request uses Basic Auth; Data API tools manage their own session (login → action → logout). The OData client retries transient failures (HTTP 429/503) with exponential backoff; the Data API client currently does not retry.
Security Notes
- stdio transport has no authentication of its own — anyone who can start the process has full access to the configured FileMaker database with the rights of the API user. Credentials live in your MCP client config (e.g.
~/.mcp.json) and are protected by filesystem permissions only. In multi-user environments, secure the server process and config file accordingly. - Startup logs to stderr include the configured host, database, and username (no password, no API keys). Redirect stderr appropriately if that is sensitive.
FM_DEBUG=truelogs the full arguments of every tool call to stderr, which may contain record data from your FileMaker database. Keep this off in production.- OData
$filtervalues passed tofm_queryare placed verbatim into the query string. Escape single quotes ('→'') in string literals yourself, and be aware that values containing URL-reserved characters (#,+,%) can corrupt the request.
Development
npm run dev # Run with tsx (no build needed)
npm run watch # Watch mode
npm run build # Compile TypeScript → dist/
npm start # Run compiled version
OData API Reference
| Operation | Method | Endpoint |
|---|---|---|
| Service Document | GET | /fmi/odata/v4/{db} |
| Metadata (EDMX) | GET | /fmi/odata/v4/{db}/$metadata |
| Read records | GET | /fmi/odata/v4/{db}/{table}?$filter=... |
| Create record | POST | /fmi/odata/v4/{db}/{table} |
| Update record | PATCH | /fmi/odata/v4/{db}/{table}({rowId}) |
| Delete record | DELETE | /fmi/odata/v4/{db}/{table}({rowId}) |
| Run script | POST | /fmi/odata/v4/{db}/Script.{scriptName} |
| Create table | POST | /fmi/odata/v4/{db}/FileMaker_Tables |
| Add field | PATCH | /fmi/odata/v4/{db}/FileMaker_Tables/{table} |
| Batch | POST | /fmi/odata/v4/{db}/$batch |
AI-generated experimental project
This MCP server was generated almost entirely with the assistance of a generative AI system and has only undergone limited human review so far. It is provided as is, without any guarantees of correctness, security, or fitness for a particular purpose. Use it at your own risk and always review and test the code thoroughly before using it in production.
The code in this repository is licensed under the MIT License. By using it, you agree that the authors and copyright holders are not liable for any claim, damages, or other liability arising from its use, as stated in the license.
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.