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

Related MCP server: filemaker-odata-mcp

Prerequisites

1. FileMaker Server with OData access enabled (Admin Console → Connectors → OData)

2. A dedicated API user with Extended Privilege fmodata

3. For Data API tools (fm_set_globals, fm_run_script_with_globals): also fmrest

4. 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

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

Data Access

Addressing a single record. FileMaker declares an OData key only for tables whose key field is validated as unique and not empty; those tables are addressed by that field's value. Every other table is addressed by its numeric ROWID, which is returned with each query result. Pass either form as rowId — quoting is handled by the server.

Scripts & Schema

Data API (Session Context)

Test & Validation

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/20 and lists disabled tools

• Recommended: always disable fm_create_table and fm_add_field on production databases

Architecture

4 files in src/:

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=true logs the full arguments of every tool call to stderr, which may contain record data from your FileMaker database. Keep this off in production.

• OData $filter values passed to fm_query are 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

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