Workbench

Workbench is the review queue for script, DATA, layout, and XML handoffs from Local MCP clients such as Codex, Cursor, Claude Desktop, or another local IDE agent.

It keeps external-agent work visible and user-controlled. MCP can stage a prompt or XML draft, but normal Workbench staging does not run providers, mutate FileMaker, or apply code during the tool call. The only exception is the explicit Local MCP beta setting Automatically create scripts in FileMaker, which can run the reviewed Create Script path for supported script stages from trusted local clients.

In-app AGENT mode uses the same local MCP tool contracts for evidence gathering, but script artifacts produced inside Genie are promoted directly into the normal CODE Preview/Copy/Apply card. They do not need a Workbench detour.

Where it appears

Open Workbench from the tool belt with the checklist icon.

Workbench items show:

• title
• mode: CODE, DATA, or LAYOUT
• source client
• status
• target script or handoff target when available
• prompt, notes, or artifact summary
• reviewer notes
• warnings
• action buttons

The top switch separates:

• Pending: items waiting for review or action
• Submitted: items already sent to Genie, with a submitted status, source label, target script, and the same visible warnings/actions where they still apply

On the Submitted tab, use the small trash button to remove all submitted items at once. Genie asks for confirmation first and leaves every Pending item untouched.

Depending on the staged item, Workbench can show:

• Run: send it through Genie
• Apply: apply a reviewed current-script artifact through the normal guarded path
• Create Script: import a supported reviewed draft as a new FileMaker script
• Preview: inspect the staged XML before acting
• Copy: copy the staged prompt or artifact
• Remove: dismiss it from the queue

When a card shows a target script, the small copy icon beside its name copies the exact staged script name for quick Script Workspace search.

MCP agents can do the same cleanup with genie_workbench action: "delete" and the item job_id. Delete only removes the staged Workbench item; it does not apply, revert, or otherwise change FileMaker.

Workbench can also receive raw XML drafts from MCP clients. In current builds, cards keep the inline view compact: the target, notes, warnings, and actions stay visible, while raw XML is opened through Preview instead of being expanded inline by default.

What happens when you run an item

Running an item does the same kind of work as sending a prompt from the composer.

Genie:

1. applies any stored metadata selection from the staged item
2. adds the prompt to chat
3. switches into the staged mode
4. enters the normal Genie pipeline

For CODE, that means scoped planning, bounded generation, preview/copy/apply review, and native Script Workspace safety still apply. For DATA, the usual confirmation and SQL guardrails still apply. For LAYOUT, generated objects stay copy-only for manual paste in FileMaker Layout mode. For External XML, the artifact was generated outside Genie, so review the XML and warnings before applying.

How MCP agents should stage work

An IDE agent should call genie_get_capabilities before staging. That capability result explains which work belongs in scripts, DATA, genie_query, layout copy output, normal planning, or manual FileMaker instructions.

For script work, the agent should use genie_scripts: read genie://schemas/script-schema or call action:get_schema, fetch targeted catalog/step/function records with get_catalog, get_steps, or get_functions, and read genie://context/scripts or action:get_context before edits. For metadata-grounded work, use genie_metadata action:parse_selection and pass the returned metadata_selection into the same staged item.

CODE staging contract

CODE Workbench items are intentionally narrow.

Stage CODE only for:

• one new FileMaker script
• one edit grounded in exact live script content or attached/selected context

Use genie_scripts for both new scripts and active-script edits. Use result_type: "new_script" for one new script, and result_type: "delta_edit" for one edit anchored against the live script context.

For delta_edit, agents should read exact live content with genie_scripts action:get_content (or use genie://context/scripts) and anchor edits to one-based numbered_text rows. merge_ready reports whether whole-script safe merge is available; merge_ready:false does not block validation or Workbench staging. Keep FileMaker Script Workspace open when you are ready to Apply. Genie verifies the exact target shown on the Workbench card before changing it. If it is already active, Apply reuses it without selecting it again; if it is different, Genie selects it first. If the target cannot be verified, Apply stops before mutation.

Workbench can hold more than one independent delta draft for the same target script. Each is reviewed and applied separately; Genie does not merge or rebase them. After applying one draft, reread exact live content and restage any later draft whose line anchors may have changed.

Do not stage:

• multiple scripts in one prompt
• create or replace script prompts
• named-script edits without exact live or attached authoring evidence
• CREATE TABLE, ALTER TABLE, INSERT, UPDATE, DELETE, TRUNCATE, or other DATA SQL
• ASK/planning prompts
• read-only QUERY prompts
• table occurrences, relationships, layouts, buttons, Web Viewers, portals, layout objects, or privilege/security work

If an IDE agent needs several scripts, it should create one genie_scripts staged item per script.

LAYOUT staging contract

Use genie_stage_layout for copy-only FileMaker layout objects. It accepts exactly one of layout, figma_import, import_json, or compiled fmxmlsnippet LayoutObjectList XML.

LAYOUT staging never creates layouts, parts, themes, fields, value lists, scripts, table occurrences, or relationships. The user reviews the item and copies the layout objects for manual paste in FileMaker Layout mode.

Whole-layout preview/proof resources are diagnostic only. Host-layout import/apply remains blocked until the required FileMaker import, rollback, visual-render, and completion-audit proof gates are satisfied.

Raw XML drafts

Raw XML staging is for agent-produced FileMaker XML drafts that should be reviewed inside Genie instead of pasted blindly from an external chat. It is useful when an MCP client has already produced a FileMaker XML artifact and Genie should keep the handoff visible in Workbench.

External XML drafts are not Stage A/B validated model output. Treat the warning banner as part of the contract: preview the XML, copy it if you want to inspect elsewhere, and apply only after you trust the artifact.

For a supported new-script draft, Create Script converts the reviewed artifact into the FileMaker import carrier only when you click the action. Genie reports the import progress and confirms when FileMaker creates the script. Unsupported conversions fail closed so you can keep using Preview, Copy, or the applicable existing Apply workflow.

DATA and QUERY routing

QUERY is not a Workbench stage. Use genie_query for read-only SELECT preview or run work outside Workbench.

Use genie_stage_data for supported FileMaker SQL writes and table/field DDL that the user will confirm in Genie. For table creation, the IDE agent should inspect Genie metadata first, stage only missing supported tables or fields, and use wording like:

Create the following tables:

Do not stage DATA prompts that rely on IF NOT EXISTS, CREATE INDEX, index-management instructions, or manual relationship/layout work.

Do not mix DATA and CODE in the same item. Script creation/editing belongs in a separate CODE stage.

For related-table DATA work, inspect relationships and fields with genie_metadata first and pass a metadata_selection bundle into genie_stage_data.

Rejections are guidance

Unsupported Workbench submissions return normal ok: false MCP results. They are not usually transport errors.

Those results may include:

• recommended_actions
• recommended_tool_calls
• recommended_resources
• stage_prompt_template
• metadata_precheck

That payload is for the IDE agent. It should inspect, split, rewrite, or present manual FileMaker instructions locally, then restage only supported Genie work.

Current MCP tools

The current external MCP staging surface uses:

• genie_get_capabilities
• genie_files
• genie_scripts
• genie_metadata
• genie_get_guides
• genie_evaluate
• genie_query
• genie_stage_data
• genie_stage_layout
• genie_workbench

Related pages

• Local MCP Bridge
• Use MCP with Your Web IDE
• Mode Behavior Matrix
• Safety and Confirmation Model