Settings

The desktop app has two levels of settings: app settings that apply globally, and project settings that apply to a single project.

Open app settings with ⌘, / Ctrl+,. Settings open as a sectioned modal with a navigation list down the left side, grouped into Workspace, Claude, Account, and (when you have plugins installed) Plugins.

App settings

Workspace

Section	What it covers
General	Core app behavior and preferences.
Appearance	Theme and skin selection (Default Dark, Light, Midnight, Terminal) built on design tokens. Toggle dark/light with ⌘T / Ctrl+T. See Design System & Skins.
Terminal	Your preferred external terminal application (e.g. Terminal.app, iTerm, Warp, WSL) used when you “open in terminal.”
Keyboard	Keyboard shortcut reference. See Keyboard Shortcuts.

Claude

Section	What it covers
AI Models	Which Claude model the app’s sessions and Conductor use.
Context	How project context is injected into Claude sessions (auto-context).
Permissions	What tools and actions Claude is allowed to run.
Skills	Manage installed skills available to Claude.
MCP Servers	Configure the Monday Morning MCP server and any additional MCP servers.

Account

Section	What it covers
Subscription	Your plan (Free / Pro / Team) and license.
Team	Team membership and seats. Shown only on the Team plan.
User Guide	In-app guide and the onboarding tour.
What’s New	Changelog for recent releases.

Plugins

Each installed plugin that declares a settings schema gets its own section here, generated automatically from that schema — credential fields (API tokens, OAuth), global config, and connection tests. See Settings & Credentials for how plugins declare these fields.

Tip

After changing plugin credentials, the MCP server does not need to restart. Tools read credentials at call time, so changes take effect immediately.

Project settings

Project settings apply to a single project and open from the Project Settings button in the Conductor header. They include:

• Project name — the display name in the rail and breadcrumb (stored in .mm/config.json).
• Project color — an accent color that tints the project’s banner and selector so the active project reads at a glance.
• Custom commands — project-level shell commands that appear as one-click chips in the Conductor, each with its own working directory and environment.
• Per-project plugin configuration — settings that vary by project (e.g. the GitHub repo, the Trello board, or the Harvest project a plugin is mapped to), defined by each plugin’s projectConfig schema.

Settings storage

App settings are persisted to localStorage in the webview and managed reactively by a Svelte 5 rune-based store. Project-level settings are written into the project’s .mm/ files. Changes save automatically — there is no explicit save button.

Next steps

• Keyboard Shortcuts — full keyboard shortcut reference.
• Desktop App Overview — the three-column shell.
• The Conductor — where project settings and briefs live.