Skip to content
Skyvern logo

Skyvern MCP server

Give your AI assistant 6 tools it can call in Skyvern, over one server URL.

Skyvern is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
6
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
September 2026

About the Skyvern MCP server

Connect Skyvern once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Skyvern and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Skyvern tools your AI can run

Once connected, your assistant can call any of these Skyvern actions by asking in plain language.

  • Run Agent Task

    Runs task with specified prompt.

    7 fields

  • Run Workflow

    Runs the workflow.

    5 fields

  • Cancel Run

    Cancels a workflow or or task run by ID.

    1 field

  • Get Workflow/Task Run

    Retrieves a workflow or task run by ID.

    1 field

  • Find Workflow

    Finds workflow based on title.

    1 field

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant Skyvern

Connect Skyvern once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Skyvern MCP, answered.

No. That is the point of it. One Activepieces server exposes Skyvern alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Skyvern in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 6 tools, including Run Agent Task, Run Workflow, Cancel Run, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.