pm_provider

Sovereign

Sovereign tier required. Both list_presets and create_preset require Sovereign. Vanguard users can manage presets through the Settings UI but not via MCP.

The pm_provider tool exposes launcher preset management over MCP. It’s the programmatic equivalent of the Settings UI — list existing presets, create new ones, and include provider defaults metadata.

For the full JSON schema and field reference, see Preset Configuration and Provider Configuration.

Actions

list_presets, create_preset, help

list_presets

List all launcher preset records.

Parameters

Field	Type	Required	Notes
`includeProviderDefaults`	boolean	No	Default `true` — also returns available provider type metadata

Example

pm_provider { action: "list_presets" }

Returns the summary shape of each preset (key, displayName, providerType, envRefs, worktree, configPreview) plus optional provider defaults.

Provider defaults are included by default. Pass includeProviderDefaults: false when you only want saved launcher presets and do not need registered provider metadata in the response.

pm_provider {
  action: "list_presets",
  includeProviderDefaults: false
}

create_preset

Create a new launcher preset.

Parameters

Field	Type	Required	Notes
`key`	string	Yes	Unique preset key
`displayName`	string	Yes	Human-readable name
`providerType`	string	Yes	Must be registered (`claude`, `codex`, `gemini`, `openai`, `anthropic`, `ollama`)
`description`	string	No
`tags`	string[]	No
`allowAdhocOverrides`	boolean	No	Default `true`
`config`	object	No	Provider-specific config object
`env`	array	No	Array of `{ name, valueRef }`
`worktree`	object	No	`{ shouldCreateWorktree?, allowReuseExistingWorktree? }`
`actor`	string	No	Who created it

Example

pm_provider {
  action: "create_preset",
  key: "coder-claude",
  displayName: "Claude Coder",
  providerType: "claude",
  description: "Claude Code preset for coding tasks",
  config: {
    model: "opus",
    permissionMode: "acceptEdits",
    keepAliveMs: 120000
  },
  env: [
    { name: "ANTHROPIC_API_KEY", valueRef: "ANTHROPIC_API_KEY" }
  ],
  worktree: {
    shouldCreateWorktree: true,
    allowReuseExistingWorktree: true
  }
}

env entries are { name, valueRef } pairs. name is the variable exposed to the provider process; valueRef names the environment or secret reference resolved at launch. Persist references, not raw secret values.

Keep raw provider secrets out of config, prompts, comments, and persisted presets. Use env refs for secret material and rely on provider config redaction for responses that echo configuration.

For the full field reference and resolution behavior, see Preset Configuration.

help

pm_provider { action: "help" }

The help payload is additive: it documents the existing pm_provider action surface and compatibility notes without changing accepted action names or input schemas.

Field	Shape	Contents
`actions`	string[]	Accepted action names: `list_presets`, `create_preset`, and `help`
`whenToUse`	object	Guidance for listing presets, creating presets, and inspecting the help payload
`examples`	array	Representative calls for default-inclusive listing, saved-preset-only listing with `includeProviderDefaults: false`, and creating a preset with an env ref
`cautions`	string[]	Secret-handling guardrails, provider config redaction expectations, and warnings against raw secrets in prompts, comments, or presets
`compatibility`	string[]	Stability notes for structured result shapes, env-ref preservation, and provider config redaction

Preset Configuration — full JSON schema and resolution rules
Provider Configuration — provider setup schema and per-provider config
pm_session.launch_task — sessions consume presets via launcherConfigKey

pm_prompt pm_knowledge

pm_provider

Actions

list_presets

Parameters

Example

create_preset

Parameters

Example

help

Related