Claude FileMaker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FM_PROTOCOL | No | Protocol for FileMaker Data API (http or https), default https | https |
| FM_SSL_VERIFY | No | Whether to verify SSL certificate (true/false), default false | false |
| FM_API_VERSION | No | API version, default v1 | v1 |
| FM_SERVER_MYDB | Yes | FileMaker server hostname for database MYDB (replace MYDB with your identifier) | |
| FM_ACCOUNT_MYDB | Yes | FileMaker account name for MYDB | |
| FM_DATABASE_MYDB | Yes | FileMaker database name for MYDB | |
| FM_PASSWORD_MYDB | Yes | FileMaker account password for MYDB | |
| NODE_TLS_REJECT_UNAUTHORIZED | No | Node TLS rejection policy, default 0 for self-signed certificates | 0 |
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_list_databasesB | List all configured FileMaker databases |
| fm_test_connectionB | Test connection to a FileMaker database |
| fm_get_metadataB | Get database metadata (layouts/tables) |
| fm_get_layout_metadataC | Get detailed metadata for a specific layout |
| fm_query_recordsB | Query records with advanced filtering and sorting |
| fm_create_recordC | Create a new record |
| fm_update_recordC | Update an existing record |
| fm_delete_recordC | Delete a record |
| fm_run_scriptD | Execute a FileMaker script |
| fm_get_scriptsC | Get list of available scripts |
| fm_clear_cacheC | Clear cached data |
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 11 tools
Each tool targets a distinct operation: listing databases, testing connections, fetching metadata at database or layout level, querying, creating/updating/deleting records, running scripts, listing scripts, and clearing cache. No two tools have overlapping purposes.
All tools follow a consistent verb_noun pattern with the fm_ prefix, e.g., list_databases, get_metadata, query_records, create_record, run_script. Even compound names like get_layout_metadata fit the pattern.
11 tools is well-scoped for a FileMaker MCP server, covering connection, metadata, CRUD, scripting, and cache management without redundancy or bloat.
The tool surface covers core CRUD, metadata retrieval, script execution, and connection testing. A minor gap is the absence of a dedicated 'get record by ID' but query_records can handle that via filters, so no critical dead ends.