plungeai_build_workflow

Creates an execution: no

https://mcp.plungeai.com/v1tools/callplungeai_build_workflow

Authorizations

Authorizationstringheader

Bearer token: Authorization: Bearer ozk_….

X-API-Keystringheader

Alternative header: X-API-Key: ozk_….

Every request needs a key, tools/list included.

Arguments

user_requeststring

The user's original request, verbatim and in their own words, before you translated it into this call. Always include it — the platform uses it for request context, routing and support diagnostics.

Maximum string length: 4000

goalstring

for a new workflow

Maximum string length: 65536

workflow_idstring

for a refine

Maximum string length: 256

instructionstring

for a refine

Maximum string length: 65536

Output

Markdown text.

Generate a new workflow from a goal, or refine an existing one (workflow_id + instruction), with the platform builder. The result is saved, so it appears everywhere (live sync).

Returns. New: Created workflow **<name>** (`<id>`). Synced to all apps. Run it with plungeai_execute_workflow. and the YAML. The name is the builder's own generated name, or the first 60 characters of the goal when the YAML has no plain name: line. Refine: Updated workflow **<name>** (`<id>`). Synced to all apps. and the YAML; the YAML is replaced in place, so save a version first if you may want to roll back. A generated workflow that fails CNL validation is not saved; the answer shows the errors and the YAML. Other errors (isError: true): Provide either `goal` (new) or `workflow_id` + `instruction` (refine)., Workflow not found: <id>, Workflow builder did not return a workflow section. It reports generating, validating and saving on the progress channel while it works (30–60 seconds).

Runs a model, costs credits and saves a workflow (not verified here):

curl -s https://mcp.plungeai.com/v1 \
  -H "Authorization: Bearer $PLUNGE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"plungeai_build_workflow","arguments":{"user_request":"build me a workflow that scans a company for acquisition news and writes a briefing","goal":"Scan a company for acquisition news and write a one-page briefing with sources."}}}'

One parameter recurs across the tools: user_request (on every tool: a string of up to 4,000 characters, optional; clients should always send it). It is described once in Recurring parameters on the MCP overview.

import json import os import requests response = requests.post( "https://mcp.plungeai.com/v1", headers={ "Authorization": f"Bearer {os.environ['PLUNGE_API_KEY']}", "Accept": "application/json, text/event-stream", "Content-Type": "application/json", }, json={ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "plungeai_build_workflow", "arguments": {}, }, }, ) for line in response.text.splitlines(): if line.startswith("data: "): print(json.loads(line[6:]))

import { Client } from '@modelcontextprotocol/sdk/client/index.js' import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js' const transport = new StreamableHTTPClientTransport(new URL('https://mcp.plungeai.com/v1'), { requestInit: { headers: { Authorization: `Bearer ${process.env.PLUNGE_API_KEY}` } }, }) const client = new Client({ name: 'my-app', version: '1.0.0' }) await client.connect(transport) const result = await client.callTool({ name: 'plungeai_build_workflow', arguments: {} }) console.log(result.content)

curl -N -X POST 'https://mcp.plungeai.com/v1' \ -H "Authorization: Bearer $PLUNGE_API_KEY" \ -H 'Accept: application/json, text/event-stream' \ -H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"plungeai_build_workflow","arguments":{}}}'

plungeai_build_workflow

Authorizations

Arguments

Output

Planned: TI-33

Planned: TI-34