@pipeworx/skyvern

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/skyvern’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 3

Run an AI browser agent against a source that publishes no API (search forms, logins, multi-step lookups) and get the extracted result back.

Tools

• skyvern_run_task(prompt, url?, data_extraction_schema?, max_steps?, wait_seconds?) — start a run described in plain language and wait up to wait_seconds (default 20) for it. Finished runs return output; unfinished ones return finished: false and a run_id.
• skyvern_get_run(run_id, wait_seconds?) — status and output of a run, optionally waiting for it. Final statuses: completed, failed, terminated, timed_out, canceled; anything else means keep polling. A failed run is returned with its failure_reason, not thrown.
• skyvern_cancel_run(run_id) — stop a queued or running run to stop per-step billing.

Typical flow: skyvern_run_task with a url and a data_extraction_schema; if finished is false, call skyvern_get_run with the run_id until it is true. Runs take seconds to minutes.

Auth

BYO only. Pass your Skyvern API key as _apiKey. Every run is billed to your Skyvern account per browser step; max_steps defaults to 25 to bound that. Without a key every tool refuses with “requires an API key” and makes no upstream call.

Data sources

• Skyvern, browser automation service — the run is executed by Skyvern in its own browsers against whatever site you point it at. What comes back is whatever that site shows; the pack adds no data of its own. The site’s terms and any login are your responsibility, as are the credentials you put in a prompt.

Notes for the next person: completed with a null output is returned with a warning rather than as a clean success. Test fixtures are synthetic documents using the field names of the vendor’s published API schema (no key was available at build); the first keyed call after deploy is the real shape check.

Tools

• skyvern_run_task — Start a Skyvern browser-agent run against a website that publishes no API (search forms, logins, multi-step lookups), described in plain language, and wait briefly for it. Returns the extracted output
• skyvern_get_run — Get the status and output of a Skyvern run by run_id, optionally waiting up to wait_seconds for it to finish. Final statuses are completed, failed, terminated, timed_out and canceled; anything else me
• skyvern_cancel_run — Cancel a Skyvern run that is still queued or running, to stop further per-step billing. Requires your own Skyvern API key as _apiKey.