Orchestrate

Orchestrate is the wizard that figures out which of your tools belong on a prompt. You point it at a prompt, template, or playbook; it searches the tools available across your Connections and Promptmark’s MCP server, ranks them against the work the prompt is actually doing, and proposes attachments with a brief rationale for each.

Orchestrate is one of four Prompty-guided wizards in Promptmark, alongside Compose, Conduct, and Guide. They share a modal-first UX – you launch the wizard inline, work through it without leaving the page, and end up back where you started.

What Orchestrate Does

Connecting MCP servers is half the job. The other half is matching the right tools to the right prompts. Without that match, your AI either ignores tools it should be using or gets distracted by tools it shouldn’t.

Orchestrate handles that matching:

• Embeds your prompt against an index of every tool you have access to
• Ranks the candidates by similarity
• Asks Prompty which tools fit, why, and – for playbooks – where in the workflow they belong
• Lets you approve, edit, or reject each proposal before anything is saved
• Attaches what you accept and bumps the prompt’s version so the change is auditable

You stay in control. Orchestrate proposes; you decide.

Opening Orchestrate

Open the wizard from any of these surfaces:

• Orchestrate in the sidebar
• The keyboard shortcut: ⌘⇧O on macOS, Ctrl+Shift+O on Windows and Linux
• The “Orchestrate with tools” button on a prompt, template, or playbook detail page
• The post-creation banner that appears after you save a new prompt

The Two Modes

Orchestrate has two modes, picked automatically based on what you point it at.

Attach (Prompts and Templates)

For prompts and templates, Orchestrate proposes a set of tools to attach to the prompt’s metadata. The flow:

1. Pick the prompt or template you want to enrich
2. Wait while Orchestrate runs the embedding search and Prompty drafts proposals (typically 2-3 seconds)
3. Review each proposal: tool name, source connection, similarity score, and Prompty’s rationale
4. Accept or reject individually, then click Attach

When you attach, Promptmark snapshots the current version of the prompt, attaches the tools, and bumps the minor version (1.0 → 1.1). The change appears in the prompt’s activity feed and version history.

Insert (Playbooks)

For playbooks, Orchestrate proposes tool-call steps to insert into the workflow. Each insertion card includes:

• The target step number and position (before, after, or inside a branch)
• The tool name and source connection
• Drafted arguments (which may reference your {{variables}})
• An optional @output(var) capture
• Prompty’s rationale for why this tool, here

You can edit the drafted arguments before accepting. When you confirm the insertions, Promptmark rewrites the playbook’s markdown to add the new step directives and snapshots the previous version.

How Tool Ranking Works

Orchestrate ranks tools by semantic similarity. The first time you run it, Promptmark indexes every available tool’s name and description as embeddings. After that, indexing is incremental – only newly discovered tools are embedded.

The ranking pipeline:

1. Embed the prompt content (or, for playbooks, the relevant step content)
2. Search the tool index for the closest matches
3. Pass the top candidates to Prompty, which decides which ones genuinely fit and writes a one-sentence rationale for each
4. Return ranked proposals with the similarity score and rationale visible

Tools without descriptions or with low similarity scores are filtered out. Prompty can also reject candidates that scored well but don’t make sense for the prompt’s actual purpose.

After Orchestrate Runs

Each Orchestrate run creates a record you can find in the prompt’s activity feed:

• Tools Attached / Tools Detached – For prompts and templates
• Playbook Tools Inserted – For playbooks

Versions are bumped (minor) so you can roll back to the pre-orchestrate state from the version history if you don’t like the result.

If the run produces no proposals, that means none of your available tools matched the prompt’s intent strongly enough. Try connecting more MCP servers via Connections, or rephrase the prompt to be more specific about the actions it expects.

Tips

• Run Orchestrate after Compose, not before. A prompt’s content has to exist for Orchestrate to embed and match against it.
• Use it on prompts you’ll actually run with tools. A prompt that’s just for reference doesn’t benefit from attachments.
• Re-run after adding a Connection. New tools need to be indexed before Orchestrate can find them. Re-running picks them up automatically.
• Edit the drafted args for playbooks. Prompty’s first draft is a starting point – adjust the variable references and JSON before accepting.

What’s Next

• Connections – Connect more MCP servers to widen the tool catalog Orchestrate can pick from
• Playbooks – The full playbook model that Orchestrate can insert tool steps into
• Compose – The wizard that drafts the prompts Orchestrate enriches