Skip to main content
Glama
datacraftdevelopment

MCP-Claude-FileMaker

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CACHE_TTLNoData cache TTL in seconds840
FM_PROTOCOLNoProtocol for FileMaker server (http or https)https
SESSION_TTLNoSession cache TTL in seconds780
FM_SSL_VERIFYNoSSL verification (true/false)false
FM_API_VERSIONNoFileMaker Data API versionv1
FM_SERVER_MAINNoFileMaker server hostname (replace MAIN with your identifier)
FM_ACCOUNT_MAINNoFileMaker account username (replace MAIN with your identifier)
FM_API_KEY_MAINNoFileMaker API key (replace MAIN with your identifier)
FM_DATABASE_MAINNoFileMaker database name (replace MAIN with your identifier)
FM_PASSWORD_MAINNoFileMaker account password (replace MAIN with your identifier)
NODE_TLS_REJECT_UNAUTHORIZEDNoTLS rejection setting (0 or 1)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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
fm_list_databasesB

List all configured FileMaker databases

fm_test_connectionC

Test connection to a FileMaker database

fm_get_metadataC

Get database metadata (layouts/tables)

fm_get_layout_metadataC

Get detailed metadata for a specific layout

fm_query_recordsC

Query records with advanced filtering and sorting

fm_create_recordD

Create a new record

fm_update_recordC

Update an existing record

fm_delete_recordC

Delete a record

fm_run_scriptC

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 11 tools

Disambiguation4/5

Most tools have clearly distinct purposes: record CRUD, script execution, connection testing, and cache clearing are unambiguous. The only mild overlap is between fm_get_metadata (database-level layouts/tables overview) and fm_get_layout_metadata (detailed metadata for a specific layout), but descriptions make the boundary reasonably clear.

Naming Consistency5/5

All tools use a consistent fm_ prefix followed by a verb_noun snake_case pattern (e.g. fm_list_databases, fm_run_script, fm_create_record). No mixed conventions or vague imperative names.

Tool Count5/5

Eleven tools is well-scoped for a FileMaker integration: it covers connection, discovery, metadata, scripts, and record lifecycle without excessive granularity. Each tool appears to earn its place.

Completeness4/5

The set covers core record CRUD (create, query, update, delete), connection testing, database listing, script execution/listing, and metadata retrieval. A minor gap is the absence of a direct get-by-id record tool, though fm_query_records can retrieve records with filtering.

Maintenance

ActivityInactive
ResponsivenessNo issues