FileMaker Data API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FM_USER | Yes | The username for authentication. | |
| FM_SERVER | Yes | The FileMaker Server hostname or IP address. | |
| FM_VERSION | No | The FileMaker Data API version (e.g., vLatest). | |
| FM_DATABASE | Yes | The FileMaker database name. | |
| FM_PASSWORD | Yes | The password for authentication. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fm_config_add_connectionB | Add a new predefined FileMaker database connection to the configuration |
| fm_config_remove_connectionB | Remove a predefined database connection from the configuration |
| fm_config_list_connectionsB | List all available predefined database connections |
| fm_config_get_connectionB | Get details of a specific connection (password is masked for security) |
| fm_config_set_default_connectionA | Set the default connection to use when the server starts |
| fm_set_connectionB | Switch to a predefined FileMaker database connection |
| fm_connectB | Connect to a FileMaker database with inline credentials (one-time connection) |
| fm_list_connectionsB | List all available predefined database connections |
| fm_get_current_connectionA | Get the currently active database connection details (password masked) |
| 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. |
| fm_logoutA | End the current FileMaker Server session |
| fm_validate_sessionA | Check if the current session token is still valid |
| fm_get_product_infoA | Get FileMaker Server product information including date/time formats |
| fm_get_databasesA | List all available databases on the FileMaker Server |
| fm_get_layoutsB | Get all layouts for a database |
| fm_get_scriptsA | Get all scripts for a database |
| fm_get_layout_metadataA | Get metadata for a specific layout including field definitions |
| fm_get_recordsB | Get records from a layout with pagination |
| fm_get_record_by_idC | Get a single record by its recordId |
| fm_create_recordB | Create a new record in a layout |
| fm_edit_recordC | Edit an existing record |
| fm_delete_recordC | Delete a record by its recordId |
| fm_duplicate_recordC | Duplicate an existing record |
| fm_find_recordsC | Find records using a query. Query is an array of search criteria objects. |
| fm_upload_to_containerC | Upload a file to a container field |
| fm_set_global_fieldsC | Set global field values |
| fm_execute_scriptB | Execute a FileMaker script from a specific layout |
| fm_upload_to_container_repetitionB | Upload a file to a container field with repetition |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.