Local MCP Bridge

Use Local MCP Bridge when you want an external editor or assistant on the same Mac to read Genie context without replacing the in-app workflow.

What it does

When enabled, Genie exposes a local MCP server on 127.0.0.1 and a port you choose in Settings.

External clients can:

read metadata resources
read current context resources
call branded read-only Genie tools

This bridge is for read access. It does not replace Genie’s native FileMaker apply flow.

Where to turn it on

Open Settings Guide and configure Local MCP Bridge.

You can control:

Enable Local MCP Bridge
Port
Status
Copy IDE JSON

Resources Genie exposes

genie://metadata/all
genie://metadata/selected
genie://context/live
genie://context/attached

Read-only tools Genie exposes

genie_get_fields_on_layout
genie_get_layout_info
genie_get_table_info
genie_get_field_info
genie_query

IDE configuration

Use Copy IDE JSON to copy a ready-to-paste configuration with the current bearer token included.

{
  "mcpServers": {
    "genie_local": {
      "url": "http://127.0.0.1:3845/mcp",
      "headers": {
        "Authorization": "Bearer <generated-token>"
      }
    }
  }
}

What users should expect from failures

When Genie cannot answer a Local MCP request because there is no active file, no usable schema, or the request is ambiguous, the response can be a normal structured result rather than a transport crash.

That means the right fix is usually to:

open the correct FileMaker file
refresh or recapture the right context
narrow the target so Genie knows what you mean

Good uses

keeping an IDE-side assistant aligned with FileMaker metadata
checking layout, table, and field details from the same machine
reading current Genie context while you work elsewhere