Skip to content
arrow_backAll articles
Guide/MetaServer/Integrations

Integrations

The Integrations page in MetaServer is the single place to install and manage every supported integration — DAWs, automation tools, and specialised Logic Pro extensions. Each integration appears as a card on the catalogue; click into a card for the per-integration detail page.

The Integrations Catalogue

The catalogue lists every integration MetaServer supports. Each card shows:

  • Icon and name — the host app the integration drives.
  • Status pill — Connected, Setup incomplete, Ready to configure, Update available, Blocked, or Not installed.
  • Version subtitle — the detected app version (or the next install step when the integration hasn't been set up yet).
  • Left accent bar — colour-matched to the status (green for Connected, amber for actionable, red for blocked).

Click any card to open its detail page.

The Detail Page

Each integration's detail page follows the same shape:

  • Header — icon, name, current status pill, and detected version.
  • Description — what the integration does and what it requires.
  • Quick Actions — pills for Help guide, Show presets in MetaGrid Pro, and About (re-opens the welcome content).
  • Integration Components card — the install / configure surface (see below).
  • Awaiting host action card (yellow, when relevant) — surfaces the next step you need to do inside the host app, like "Open Cubase and confirm MetaGrid Pro is selected in the MIDI Remote panel."
  • Details expander — collapsed by default; opens to per-component diagnostics, version info, and bulk Reinstall / Uninstall buttons.

Integration Components Card

This is where setup happens. Components are grouped into sections (Cubase / Nuendo, for example, group into MIDI Remote, PLE / LE Presets, and Generic Remote Devices); other integrations show a flat component list.

Each row offers a state-driven action button:

  • Install — install a missing component. The button auto-transitions to a spinner during the install, then a green checkmark on success.
  • Reinstall — overwrite an installed component with the current bundled version.
  • Locate… — open a file picker (for components that point at a user-chosen file, like Cubase's Generic Remote macro slots or Dorico's key commands JSON).
  • Download — copy a bundled file to your Downloads folder and reveal it in Finder (used by REAPER's keymap, DP's keybindings, Cubase's Generic Remote XMLs, and the Logic Pro MIDI Transform Sets).

Optional rows surface a section-level Optional pill on their group header (e.g., Cubase Generic Remote Devices). If a pointed-at file goes missing, the row shows File not found at the saved location with both a Reinstall button (re-download the bundled file and re-point) and Locate… button (pick a custom file).

Refresh

A Refresh button at the top of every detail page re-runs detection across every component. Use it after making changes inside the host app (renaming a Cubase macro, importing a new keybinding) so MetaServer re-reads the underlying files.

Per-Integration Setup

See the individual integration pages for in-app configuration: