How do I use MCP_RCC_SP?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP_RCC_SP show me all clients in the database" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

MCP_RCC_SP

by datacraftdevelopment

Overview Schema Related Servers Score Discussions

TypeScript

Remote

FileMaker MCP Server - RCC Starting Point

A Model Context Protocol (MCP) server for FileMaker databases, providing comprehensive database access through dynamic script discovery, full CRUD operations, and OData query capabilities with flexible authentication methods.

Features

🎯 Core Capabilities

Dynamic Script Discovery: Automatically discovers and exposes FileMaker scripts using the GetToolList pattern
Full CRUD Operations: Create, Read, Update, Delete records across any layout
OData Support: Advanced querying with filtering, sorting, and pagination
Flexible Authentication: Supports API key, basic auth, and Otto proxy authentication
Multi-Database Ready: Configurable for any FileMaker server deployment

🔧 Key Advantages

Graceful Degradation: Works with or without GetToolList script - CRUD always available
TypeScript First: Full type safety and modern development experience
Caching & Performance: Intelligent caching for sessions, data, and script discovery
Production Ready: Comprehensive error handling, logging, and configuration validation
Web App Ready: Designed for integration with web applications and chatbots

Related MCP server: Database MCP Server

Quick Start

Prerequisites

Node.js 18+
Access to a FileMaker Server with Data API enabled
Valid authentication credentials (API key, username/password, or Otto proxy)

Installation

# Install dependencies
npm install

# Copy and configure environment variables
cp .env.example .env
# Edit .env with your FileMaker server details

# Build and start
npm run build
npm start

Configuration

The MCP server is configured via environment variables in the .env file:

# Example Database Configuration
FM_NAME=YourDatabase
FM_HOST=https://your-filemaker-server.com
FM_DATABASE=YourDatabaseName

# Authentication (choose one method)
FM_AUTH_TYPE=basic
FM_USERNAME=your_username
FM_PASSWORD=your_password

# Or use API key authentication
# FM_AUTH_TYPE=apikey
# FM_API_KEY=your-api-key-here

# Layouts and Features
FM_LAYOUTS=API_Client,API_Project,API_Task
FM_DEFAULT_LAYOUT=API_Client
FM_ENABLE_SCRIPT_DISCOVERY=true
FM_ENABLE_ODATA=true
FM_DEFAULT_API=data_api

# Logging and MCP Settings
LOG_LEVEL=info
MCP_CLEAR_CACHE_ON_STARTUP=true

GetToolList Script Implementation

For dynamic script discovery, implement this FileMaker script named "GetToolList":

# GetToolList Script (FileMaker)
# Purpose: Return JSON describing available scripts for MCP

Exit Script [
  Text Result: 
  "{
    \"tools\": [
      {
        \"name\": \"send_email\",
        \"description\": \"Send email notification to client\",
        \"parameters\": [
          {\"name\": \"client_id\", \"type\": \"string\", \"required\": true, \"description\": \"Client record ID\"},
          {\"name\": \"message\", \"type\": \"string\", \"required\": true, \"description\": \"Email message content\"},
          {\"name\": \"urgent\", \"type\": \"boolean\", \"required\": false, \"description\": \"Mark as urgent\"}
        ]
      },
      {
        \"name\": \"generate_report\",
        \"description\": \"Generate project status report\", 
        \"parameters\": [
          {\"name\": \"project_id\", \"type\": \"string\", \"required\": true, \"description\": \"Project ID\"},
          {\"name\": \"include_financials\", \"type\": \"boolean\", \"required\": false, \"description\": \"Include financial data\"}
        ]
      }
    ]
  }"
]

Usage Examples

With Claude Desktop

Add to your Claude Desktop MCP settings:

{
  "mcpServers": {
    "filemaker-enhanced": {
      "command": "node",
      "args": ["/path/to/MCP-Claude-FileMaker-Enhanced/dist/index.js"],
      "env": {
        "MCP_CONFIG_FILE": "/path/to/config/databases.json"
      }
    }
  }
}

Available MCP Tools

The server automatically provides these tools to Claude:

CRUD Operations

fm_find_records - Search and retrieve records
fm_get_record - Get single record by ID
fm_create_record - Create new record
fm_update_record - Update existing record
fm_delete_record - Delete record

OData Queries (if enabled)

fm_odata_query - Advanced filtering and sorting
fm_odata_metadata - Get database schema info

Dynamic Scripts (via GetToolList)

Custom script tools based on your GetToolList implementation
Parameters automatically validated and typed

Management Tools

fm_list_layouts - Get available layouts
fm_get_database_info - Database metadata
fm_health_check - Connection status

Advanced Configuration

Authentication Methods

# Basic Authentication
FM_AUTH_TYPE=basic
FM_USERNAME=username
FM_PASSWORD=password

# API Key Authentication
FM_AUTH_TYPE=apikey  
FM_API_KEY=your-api-key

# Otto Proxy Authentication
FM_AUTH_TYPE=otto
FM_OTTO_URL=https://otto-proxy.com

Caching Configuration

# Session cache (13 minutes default)
SESSION_TTL=780

# Data cache (14 minutes default) 
DATA_TTL=840

# Script discovery cache (30 minutes default)
SCRIPT_TTL=1800

Logging Options

# Log level: error, warn, info, debug
LOG_LEVEL=info

# Optional log file (defaults to console)
LOG_FILE=/var/log/filemaker-mcp.log

Architecture Overview

┌─────────────────────────────────────────────────────────────┐
│                    Enhanced FileMaker MCP                    │
├─────────────────────────────────────────────────────────────┤
│  Claude Desktop  ←→  MCP Protocol  ←→  FileMaker Server     │
├─────────────────────────────────────────────────────────────┤
│                        Components                           │
│  • ConfigManager      - Multi-database configuration       │
│  • AuthManager        - Flexible authentication           │ 
│  • DataClient         - CRUD operations with caching      │
│  • ODataClient        - Advanced querying capabilities    │
│  • ScriptDiscovery    - Dynamic tool generation           │
│  • Logger             - Comprehensive logging             │
└─────────────────────────────────────────────────────────────┘

Key Design Decisions

GetToolList Pattern: Curated script exposure with graceful fallback
TypeScript First: Full type safety throughout the codebase
Caching Strategy: Multi-level caching for optimal performance
Error Resilience: Comprehensive error handling and recovery
Configuration Flexibility: Support for simple and complex deployments

Troubleshooting

Common Issues

Connection Errors

# Check FileMaker Server status
curl -k https://your-server.com/fmi/data/v1/databases

# Verify credentials
npm run test -- --grep "authentication"

Script Discovery Issues

# Test GetToolList script directly in FileMaker
# Should return valid JSON with tools array

# Check script discovery cache
LOG_LEVEL=debug npm start

Performance Issues

# Enable query logging
DEBUG_FILEMAKER_QUERIES=true npm start

# Check cache hit rates
LOG_LEVEL=info npm start | grep "cache"

Development

Project Structure

src/
├── core/
│   ├── auth.ts           # Authentication management
│   ├── config.ts         # Configuration loading/validation  
│   ├── data-client.ts    # FileMaker Data API client
│   └── logger.ts         # Logging utilities
├── adapters/
│   ├── odata.ts          # OData query adapter
│   └── script-discovery.ts # Dynamic script discovery
├── types/
│   └── filemaker.ts      # TypeScript type definitions
└── index.ts              # Main MCP server

config/
├── databases.json        # Multi-database configuration
└── sample-*.json         # Configuration examples

docs/
├── getToolList.md        # GetToolList implementation guide
└── examples/             # Usage examples and FileMaker scripts

Building and Testing

# Development with hot reload  
npm run dev

# Build for production
npm run build

# Run tests
npm test

# Lint and format
npm run lint
npm run format

Contributing

Fork the repository
Create a feature branch (git checkout -b feature/amazing-feature)
Commit your changes (git commit -m 'Add amazing feature')
Push to the branch (git push origin feature/amazing-feature)
Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

Documentation: Full docs in the /docs folder
Issues: GitHub Issues
Discussions: GitHub Discussions

Acknowledgments

Anthropic for the Model Context Protocol specification
FileMaker Community for FileMaker Data API best practices
ProofGeist for FileMaker API patterns and inspiration
Original MCP Contributors for foundational MCP implementation patterns

This server cannot be installed

license - permissive license

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

–Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/datacraftdevelopment/MCP_RCC_SP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server