Use MCP with Your Web IDE

This example shows how Genie can expose FileMaker-aware context to an editor or agent running on the same Mac, then accept reviewed handoff through Workbench.

Goal

Enable Local MCP Bridge, connect the IDE, inspect metadata, and stage one supported script or DATA Workbench item without bypassing Genie review.

Suggested flow

1. Open Settings Guide.
2. Enable Local MCP Bridge.
3. Choose the setup guide format for your client.
4. For Codex, copy the Streamable HTTP TOML snippet into ~/.codex/config.toml. For Cursor or generic clients, copy the JSON snippet.
5. Restart or reload the IDE client so it discovers the MCP server.
6. Ask the IDE agent to call fm_session action:status when it needs session identity.
7. For script work, have the agent discover Script Schema and targeted step/function records with fm_search, then read the exact script with fm_read target:script (or genie://context/scripts) before edits.
8. Have the agent inspect one exact metadata target with fm_read.
9. If the prompt names several metadata objects for staging, call fm_read target:selection with their exact identities.
10. Stage exactly one item with fm_stage kind:script, kind:data, or kind:layout.
11. Open Workbench in Genie and run, copy, or remove the staged item.

Example staging request

For one new script, submit a Script Schema document to fm_stage kind:script. The steps array should use step ids/names and argument shapes discovered with targeted fm_search queries.

{
  "kind": "script",
  "title": "Export Customers JSON",
  "source": "Codex",
  "script": {
    "result_type": "new_script",
    "script": {
      "name": "Export Customers JSON",
      "steps": [
        {
          "name": "Set Variable",
          "args": {
            "name": "$json",
            "value": "\"[]\""
          }
        }
      ]
    }
  },
  "metadata_selection": {
    "tables": [],
    "fields": [],
    "layouts": [],
    "scripts": [],
    "customFunctions": []
  }
}

For an edit, read genie://context/scripts or fm_read target:script first and submit fm_stage kind:script with result_type: "delta_edit". For one supported SQL data/schema request, use fm_stage kind:data.

If the agent receives ok: false, it should follow the returned guidance. For example, a bundled two-script request should be split into two fm_stage kind:script calls, one per script.

What belongs in the demo

• setup guide format selection in Settings
• Codex Streamable HTTP or Cursor/generic JSON configuration
• fm_session action:status when session identity matters
• Script Schema and targeted script catalog/step records discovered with fm_search
• one exact fm_read lookup
• one metadata_selection bundle from fm_read target:selection when metadata names matter
• one staged Workbench item
• user review in Workbench
• normal Genie CODE or DATA behavior after clicking Run

Boundaries to mention

• MCP staging does not generate, mutate, or apply.
• Script work is one new script or one active-script edit through fm_stage kind:script.
• DATA is one supported FileMaker SQL write/schema request through fm_stage kind:data.
• QUERY is read-only SELECT through fm_query, outside Workbench.
• ASK/planning stays in the IDE or normal Genie chat, outside Workbench.
• Manual FileMaker graph and layout work stays in FileMaker or in IDE-side instructions.

Suggested media

• one short walkthrough video
• one screenshot of Local MCP Bridge settings with setup guide
• one screenshot of the copied Codex TOML or Cursor JSON
• one screenshot of the external MCP client reading Genie metadata
• one screenshot of a staged Workbench item
• one screenshot of Genie running the item through normal chat