FileMaker MCP Server
@mw777eds
About FileMaker MCP Server
Local dynamic mcp server for FileMaker databases
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"filemaker_mcp_local": {
"command": "python3",
"args": [
"-m",
"venv",
"venv"
]
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
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.
Frequently asked questions
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.
Basic information
More Other MCP servers

Glasswarp
GlasswarpSee and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.
Inbox Zero AI MCP
elie222The world's best AI personal assistant for email. Open source app to help you reach inbox zero fast.
AutoBrowser MCP
autobrowser-aiBrowser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
Production-ready MCP integrations for AI applications
Klavis-AIKlavis AI: MCP integration platforms that let AI agents use tools reliably at any scale
Activepieces
activepiecesAI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
Comments