Claude FileMaker MCP Server
Related Servers
Alternatives to Claude FileMaker MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that provides AI assistants with direct access to FileMaker databases via OData v4 API, enabling CRUD operations, script execution, and schema introspection.196MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for FileMaker Server OData 4.01 API integration, enabling AI assistants to discover databases, perform CRUD operations, and manage connections.20 npm13MIT
- AlicenseAqualityCmaintenanceMCP server for Claude that connects to MySQL, MariaDB, and SQLite databases. Query your databases using natural language.3MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that connects to open data portals like CKAN and Socrata, enabling natural language querying of datasets via Claude.MIT
- AlicenseAqualityDmaintenanceAn MCP server implementation that integrates Claude with Salesforce, enabling natural language interactions with Salesforce data and metadata.881 npmMIT
- AlicenseAqualityAmaintenanceAn MCP server implementation that integrates Claude with Salesforce, enabling natural language interactions with Salesforce data and metadata for querying, modifying, and managing objects and records.151,592 npm166MIT
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.