plungeai_list_workflows

Read-onlyCreates an execution: no

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

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

searchstring

Maximum string length: 2000

folderstring

Maximum string length: 2000

limitinteger

Default: 50

Required range: 1 <= x <= 100

formatenum<string>

markdown (default): rendered for an AI reader · json: the same outcome as a JSON document in text plus structuredContent

Available options: markdown, json

Default: markdown

Output

Markdown text; format: "json" returns the same answer as a JSON document.

List your saved workflows, which is what users usually mean by "my agents". With no filters it shows your folders (rubrics) and your most recent workflows; filter with folder and/or search.

Returns. Without filters: # Your Workflows (N most recent), a Folders: line with every non-empty folder and its count, and a table: Name, Kind, Folder, ID, Description. With filters: # Your Workflows (N) and the same table. No workflows found. … / No workflows matched. … when empty. JSON: {"workflows": [{id, name, description, kind, folder}]}.

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_list_workflows","arguments":{"user_request":"show me my workflows in the Finance folder","folder":"Finance","format":"json"}}}'

Two parameters recur across the tools: user_request (on every tool: a string of up to 4,000 characters, optional; clients should always send it) and format (markdown by default, or json). Both are 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_list_workflows", "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_list_workflows', 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_list_workflows","arguments":{}}}'

plungeai_list_workflows

Authorizations

Arguments

Output

Planned: TI-33

Planned: TI-34