Prompt template MCP tools

Prompt template tools let MCP clients list, read, create, update, delete, and export Solo prompt templates. They are off by default; enable the Prompt template MCP tools toggle in Settings > MCP to expose them.

Tools#

• list_prompt_templates — List template summaries from the global scope plus the effective project's template pool. Optional query filters by name and description, and sort accepts picker (default), name, updated, created, or last_selected. Listing does not update a template's last-selected time.
• get_prompt_template — Read one template by template_id, including its full body and parsed placeholders. Reading a template updates its last-selected time.
• create_prompt_template — Create a template with name and a Markdown body, plus an optional description. Omit project_id to create a global template, or pass it to create a project-scoped template. Creation uses the same validation and same-scope name uniqueness rules as the app.
• update_prompt_template — Patch a template's name, description, and/or body without changing its scope. Omitted fields are preserved; an empty string clears the description or body.
• delete_prompt_template — Delete one template by template_id.
• export_prompt_templates — Export the templates listed in template_ids as Markdown files with frontmatter into destination_dir, which Solo creates when missing. Filenames follow the same slugging and duplicate-numbering rules as the app's export command.

Notes#

The settings toggle only controls MCP visibility. Prompt templates stay fully available in the rest of Solo either way.

When a primary project is deleted through delete_project, the default delete policy removes its project-scoped templates; prompt_template_policy: "convert_to_global" moves them into the global pool instead. Deleting a linked checkout leaves the primary project's shared template pool unchanged. See Project tools.

For the prompt template feature itself, including placeholders and in-app editing, see Prompt templates.