Skip to main content
Glama
datacraftdevelopment

MCP-Claude-FileMaker

by datacraftdevelopment
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP-Claude-FileMaker

No user-submitted related servers found.

    Related Servers

    • FileMaker Data API MCP Server

      fsans
      A
      license
      B
      quality
      D
      maintenance
      Provides AI agents with direct access to FileMaker databases through the FileMaker Data API, enabling natural language interactions for querying, managing records, and database introspection.
      28
      6 npm
      3
      MIT

    • Claude FileMaker MCP Server

      ayushshah31
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that connects Claude to FileMaker databases via the Data API, enabling natural language queries, record management, layout exploration, and script execution.
      11
      MIT

    • MCP Database Server

      lukhim
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to query and manage databases (SQLite, SQL Server, PostgreSQL, MySQL) through natural language, supporting read/write operations and schema management.
      544 npm
      MIT

    • Dataverse MCP Server

      LosslessFunction
      F
      license
      A
      quality
      D
      maintenance
      Enables direct interaction with Microsoft Dataverse from Claude Desktop, supporting full CRUD, bulk operations, FetchXML queries, actions, and metadata discovery.
      20
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources