Skip to main content
Octoparse templates are available through the website, desktop app, CLI, MCP, and API. The website provides a quick way to run a template in the cloud. The desktop app provides more convenient control over task setup and supports more run options, including Local Extraction and Cloud Extraction when they are available for the template. CLI, MCP, and API bring templates into command-line, AI, and application workflows. The available interface and run mode can vary by template. This page explains what each option supports and where it fits.

​
Choose an interface

Only templates that support Cloud Extraction can run on the Octoparse website or through MCP and API. Templates that support Local Extraction only must be run in the desktop app.

​
Website

On the Octoparse website, you can find a template, read its instructions, enter the required parameters, and run it in the cloud. If a template supports Local Extraction only, you can download the Octoparse desktop app to continue.

​
Desktop app

In the desktop app, you can configure the template inputs and choose how the task runs. Local Extraction runs the task on your computer. Cloud Extraction runs it on Octoparse cloud resources when the template and your account support this option. A template that supports Local Extraction only must be run in the desktop app. See Local vs. cloud extraction for a detailed comparison of the two run modes.

​
CLI

The CLI is useful when template discovery and task creation need to be repeatable or included in a script. Authenticate first, then search the catalog, inspect the normalized parameters, and create a template-based task.

Create tasks from templates with the CLI

See the current commands, parameter formats, and next steps for running the created task.

​
MCP

Use Octoparse MCP from an MCP-compatible AI client to search for templates and run them through natural-language requests. MCP can execute only templates that support cloud execution; local-only templates must be run from the desktop app.

Search templates with MCP

Find candidates by keyword or target website.

Run a template with MCP

Create a cloud task, run it, and retrieve the result.

​
API

The API supports applications and automated workflows that need to find and run templates programmatically. The template search response provides the input schema required for execution, while the task endpoints support running, monitoring, and exporting the result.

Search templates with the API

Find matching templates and inspect their input schemas.

Run a template with the API

Create and start a task from the selected template.

​
Before automating a template

Test the exact template and inputs you plan to use. Confirm the output fields, execution method, permissions, expected volume, and error behavior before scheduling recurring runs or connecting the result to another system.