Run a reviewed pipeline from an MCP client

Connect through MCP setup, then discover recipes using data_catalog with {"kind":"recipe","limit":20}. Inspect the selected recipe with data_describe. Its native-generated examples and schema describe the current request contract.

For a saved summary, select an accessible source dataset and a supported sink_ output dataset. Prepare a plan:

{
  "recipe": "dataset-summary",
  "input_dataset": "<accessible source>",
  "output_dataset": "sink_research_summary",
  "parameters": {"group_by": ["<declared field>"], "function": "count", "output_limit": 50},
  "limits": {"max_scan_rows": 1000, "max_scan_bytes": 1048576, "timeout_ms": 10000, "max_charge_microusd": 100000, "max_storage_bytes": 1048576}
}

Preparation reports effects, revisions, the immutable price and maximum charge without executing work. If those fit the user's task and spending authority, call pipeline_run with {"prepared_ref":"<returned plan>","idempotency_key":"research-42-summary"}. Poll pipeline_status, then read a bounded pipeline_results page. Complete output carries an owner-scoped dataset and output receipt. Partial scans do not publish a complete summary.

search-to-dataset combines one existing search connector with native persistence. Its parameters are query, provider and max_results; its output is agent_search_result_v1. The limits must include an authorized connector allowance and storage allowance. Supplier charges are allocated from the parent run reservation and included once in the final charge. The original stored supplier delivery is reused on recovery.

For recurrence, use pipeline_host with action prepare, the accepted preparation, interval and daily/monthly budgets. deploy performs a paid smoke run and leaves the host ready_paused; only an explicitly requested activate starts scheduling. Every control mutation uses a stable idempotency key. Pause disables future admissions. Rollback re-verifies the prior accepted revision and returns paused without undoing existing outputs.

Use the data and pipeline tools for the prepare/quote/run workflow above. The hosted server also exposes api_search, api_describe and api_call for declared API operations, including agent and approval APIs where the deployment and caller permit access; their existing authorization and approval rules still apply. Browser change-monitor recipes appear in discovery only after their separate connector integration is available.