Additional resources

Application resources

  • Privacy policy - Available in the application footer—outlines how your data is handled and protected

  • Terms of service - Linked from the application footer—details usage terms and conditions

Technical documentation

  • FileMaker Data API Guide - Comprehensive guide to the FileMaker Data API

    • Essential for understanding database connectivity requirements

    • Covers authentication, data formats, and API limitations

  • FileMaker Security Guide - Describes the security features available with the FileMaker Platform and the steps you can take as a custom app developer, a server administrator, or an IT professional to apply these security features to your FileMaker custom apps.

  • FileMaker Server Help - Comprehensive guide to FileMaker Pro for creating custom apps

  • FileMaker Pro Help - Comprehensive guide to FileMaker Server for hosting custom apps

  • MCP Specification - Official Model Context Protocol documentation

    • Explains the protocol standards and implementation details

    • Useful for developers building custom MCP clients

    • Provides technical specifications for integration

Developer tools

For advanced users and developers, there are optional open-source tools available to assist with testing and debugging MCP behavior. These tools are not developed or maintained by Claris, but can provide valuable insights during development and testing.

MCP Inspector

The MCP Inspector is an interactive developer tool for testing and debugging MCP servers. It runs directly through npx without requiring installation.

  • Requirements - Node.js with npm version 5.2.26 or higher

  • GitHub Repository - https://github.com/modelcontextprotocol/inspector

  • Usage Note - The inspector uses the bearer scheme to send tokens. Context (static) tokens cannot be used with the inspector without customization.

  • Testing URL - https://mcp.dev.connect.claris.com/sse

Fast agent

fast-agent lets you create and interact with sophisticated Agents and Workflows in minutes. It's multi-modal, supporting Images and PDFs in Prompts, Resources and MCP Tool Call results.

  • Requirements - Python and uv (a package manager for Python applications)

  • GitHub Repository: https://github.com/evalstate/fast-agent

  • Token Support - Context (static) tokens can be used with the scheme of "static" instead of "bearer"

Claude Desktop

Claude Desktop supports remote MCP servers through their developer configuration, which can be accessed from the Settings > Developer tab.

One way to connect to remote MCP servers from Claude is to use Node.js modules such as remote-mcp. The following is an example configuration using npx and remote-mcp to connect to the Claris MCP Service

Copy 
{
  "allowDevTools": true,
  "mcpServers": {
    "claris_mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@atest",
        "https://mcp.connect.claris.com/org/{{orgId}}/ctx/{{ctxId}}/sse",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Static {{staticToken}}"
      }
    }
  }
}

If using npx, you must have Node.js version 22 or later installed and available in your path. Additionally, Claude will use the earliest version of Node.js found in the paths available to it. View the logs from the MCP server to see the paths Claude will use.

For example:

Copy 
2025-07-23T20:38:12.307Z [claris_mcp] [info] Using MCP
server command: /opt/homebrew/bin/npx with args and path: {
  metadata: {
    args: [ 
      'mcp-remote', 
      'https://mcp.connect.claris.com/org/{{orgId}}/ctx/{{ctxId}}/sse', 
      [length]: 2 
    ],
    paths: [
      '/usr/local/bin',
      '/opt/homebrew/bin',
      '/usr/bin',
      '/usr/bin',
      '/bin',
      '/usr/sbin',
      '/sbin',
      [length]: 7
    ]
  }
}

For more information, see Connect Claude Code to tools via MCP in Claude Docs and Connect to remote MCP servers in Model Context Protocol documentation.

Note  As of now, we recommend not using Claude Sonnet 4.5 as our experience shows it is not yet stable with Claris MCP.

Support resources

Getting help

For technical support or additional questions about using Claris MCP:

  1. System administrator - Consult your internal system administrator for:

    • Network connectivity issues.

    • FileMaker Server configuration.

    • Security and access policies.

    • Environment-specific troubleshooting.

  2. Claris Documentation - Consult official Claris documentation resources for:

    • FileMaker Server issues.

    • FileMaker Data API issues.

    • FileMaker Pro file account issues.

    • General information.

  3. Claris Support - Contact official Claris support if you're unable to resolve your issue after consulting documentation.

Community resources

  • Claris Community - Official forums and user groups

  • FileMaker Developers - Technical community for advanced topics

  • MCP Developer Community - Growing community around Model Context Protocol implementations

  • FileMaker - The underlying database platform powering your connections.

Feedback and contributions

Providing feedback

If you encounter issues or have suggestions for improving Claris MCP:

  1. Bug reports - Document specific issues with:

    • Steps to reproduce the problem.

    • Expected vs. actual behavior.

    • Environment details (server versions, network configuration).

    • Screenshots or error messages.

  2. Feature requests - Suggest improvements including:

    • Use case description.

    • Business impact and benefits.

    • Proposed implementation approach.

    • Integration requirements.

  3. Documentation - Help improve these guides by:

    • Reporting unclear or missing information.

    • Suggesting additional examples or use cases.

    • Contributing corrections or updates.

    • Sharing successful implementation stories.

    For bug reports and feature requests, contact Claris support.

    For documentation feedback, click the feedback link at the bottom of any documentation page to open the documentation feedback form.

Staying updated

  • Monitor official Claris channels for product updates.

  • Subscribe to relevant technical newsletters and blogs.

  • Participate in user community discussions.

  • Attend Claris conferences and webinars for latest developments.