StewAI

com.stewai/stewai

Discover, run, inspect, build, test, and privately reuse AI workflows.

Yes, your AI can use this right now.Answered a live MCP handshake in 581 ms with no sign-in needed and exposes 14 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://api.stewai.com/mcp

14 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
check_recipe_buildread-only

Run free deterministic lint, render, policy, and compiler checks. Omit fixtures for the normal structural check; a supplied fixture probe must also provide every referenced upstream dependency value.

commit_recipe_buildcan modify

Preflight and privately publish only the exact fully qualified recipe revision. A successful commit returns a private editor URL and, when current run access permits it, a recipe_ref. Preview that reference before any dry run: authoring contract handles and node IDs are not the positional input_N run handles. The recipe stays private, unlisted, and unreviewed; commit never lists, prices, or publis

discover_stewairead-only

Learn how any MCP agent can authenticate, discover, preview, run, author, qualify, commit, inspect, and recover StewAI recipes. Call this first.

get_recipe_buildread-only

List or inspect only the authenticated creator's private recipe builds. To list builds omit both build_ref and view; limit/cursor paginate that list. With or without build_ref, use view='authoring_schema' and schema_name='update_recipe_build', 'acceptance_suite', or 'start_recipe_build' to read the complete executable JSON Schema when a client hides nested operation or assertion fields. Large acce

get_recipe_build_activityread-only

Poll a review or acceptance batch through a bounded, disclosure-safe view.

get_recipe_previewread-only

Inspect a safe summary with bounded method and limitations excerpts, output-contract state, and evidence context. For complete authorized published details and executable contracts, use view=details. Concatenate content fragments in offset order per section; decode JSON sections after completion. Use next_cursor with the same recipe_ref until null. Opaque internals remain withheld.

get_resultsread-only

After a finished run, read view=steps with detail=full first and follow next_cursor; every step the user paid for is part of the result. Declared outputs are the pinned summary, not the whole result. Read declared outputs or a sanitized per-step trace from an owned run, including signed chunks for oversized steps. view=steps returns compact summaries, 10 per page by default and at most 20 (limit 1

get_runread-only

Read an owned run, view=history to resume normal runs (recipe_ref/status/cursor/limit), or view=diagnostics for its settled UI receipt. Default status requires run_id and includes live progress: updated_at is the run record time, progress.last_step_activity_at is the latest step activity. A blocked run paused for credits reports credit_pause.

review_recipe_build

Quote or run a bounded semantic quality review of the exact private draft revision.

run_recipecan modify

Estimate or run a previewed public or account-authorized published recipe. dry_run foregrounds history (recent charges or median and p90), fees, balance, and can_start. safety_ceiling_credits is a pathological bound when available, not a quote or admission threshold; a null ceiling means provider search has no request-side query limit and does not block a run. estimated_credits and sufficient are

run_recipe_acceptance

Quote or run selected or complete behavioral acceptance cases for an exact private draft revision. Quotes explain enforced input bounds, output caps and retry allowances in acceptance_cost. Preserve representative fixtures and assertions; remove unnecessary model stages rather than weakening tests to lower a quote. Paid work requires an approved budget. A full run that needs user approval returns

search_recipesread-only

Find safe public recipes and published recipes available to the current account. results are direct fits (exact or strong); related_results are adjacent recipes, not direct fits. Each row states its output contract, past-run cost history and, for reviewed public recipes, that safety review is not output-quality validation. required_inputs and required_outputs match exact handles or normalized labe

start_recipe_build

Create a private recipe build from a bounded intent and declared contract. Recipe inputs are strings: use type:string, positive maxLength, and only minLength:1 on required inputs. Richer input constraints must be handled in recipe logic and tested, not claimed as enforced by the input node. The response returns the stored contracts when they fit the bounded result; the archetype bundle is optional

update_recipe_buildcan modify

Apply bounded optimistic changes to an owned private recipe build. After an uncertain response, inspect the build and replay the identical request with the same idempotency key; a new key duplicates the work. Use only the exact op names and payload keys in inputSchema: set_metadata takes metadata, upsert_schema takes schema_id and schema, and acceptance uses set_acceptance_cases with suite. Never

Alternatives in Search & Research

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”