FileMaker MCP Server

What is FileMaker MCP Server?

FileMaker MCP Server dynamically exposes FileMaker scripts as tools via the Model Context Protocol (MCP), with a Gradio web interface for interacting with those tools. It is built for developers who want to integrate FileMaker script execution into MCP-compatible AI workflows.

How to use FileMaker MCP Server?

Clone the repository, create a Python virtual environment, install dependencies from requirements.txt, configure FileMaker credentials in a .env file (FM_USERNAME, FM_PASSWORD, FM_HOST, FM_DATABASE, FM_LAYOUT), and run python gradio_mcp_server.py. This starts the MCP server on stdin/stdout and a Gradio UI on port 7860.

Key features of FileMaker MCP Server

• Dynamically exposes FileMaker scripts as MCP tools
• Provides a Gradio web UI for tool interaction
• Supports MCP protocol over stdin/stdout
• Configuration via environment variables for authentication
• Requires only a FileMaker layout and credentials to run

Use cases of FileMaker MCP Server

—

FAQ from FileMaker MCP Server

What does this server do?

It dynamically exposes FileMaker scripts as tools that can be invoked through the Model Context Protocol, and provides a Gradio web UI for browsing and testing those tools.

What are the runtime dependencies?

Python 3 with a virtual environment, the packages in requirements.txt, and valid FileMaker credentials (username, password, host, database, and layout) provided via a .env file.

How is the server accessed?

The MCP server communicates via stdin/stdout. The Gradio UI is served on the local machine, typically at port 7860, and can be opened in a browser.

What transport does the MCP server use?

It uses the MCP protocol over standard input/output (stdin/stdout).

What authentication is required?

FileMaker credentials (FM_USERNAME, FM_PASSWORD, FM_HOST, FM_DATABASE, FM_LAYOUT) must be set in a .env file in the project root.