FileMaker MCP Server

Created By
mw777edsa year ago
Local dynamic mcp server for FileMaker databases
Overview

what is FileMaker MCP Server?

FileMaker MCP Server is a dynamic server that implements the Model Context Protocol (MCP) to expose FileMaker scripts as tools, allowing for easy interaction through a web interface.

how to use FileMaker MCP Server?

To use the FileMaker MCP Server, clone the repository, set up a virtual environment, install the required dependencies, configure your FileMaker credentials in a .env file, and run the server script to start the service.

key features of FileMaker MCP Server?

  • Dynamic exposure of FileMaker scripts as tools
  • User-friendly interface powered by Gradio
  • Easy setup and configuration for FileMaker databases

use cases of FileMaker MCP Server?

  1. Automating tasks in FileMaker databases through exposed scripts.
  2. Providing a web interface for users to interact with FileMaker tools.
  3. Integrating FileMaker functionalities into other applications via the MCP protocol.

FAQ from FileMaker MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that allows for dynamic interaction with tools and scripts in FileMaker databases.

  • Do I need to have FileMaker installed to use this server?

Yes, you need to have access to a FileMaker database to utilize the MCP server.

  • Is there a graphical interface for the server?

Yes, the server provides a web UI through Gradio for easy interaction.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mw777eds
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago