Octoparse MCP Server

Octoparse MCP Server

English | 日本語

Octoparse MCP Server connects MCP-compatible AI clients to Octoparse so users can discover scraping templates, create cloud tasks from Octoparse preset templates, manage existing tasks, and export structured data.

Hosted Server

Use the hosted Streamable HTTP endpoint:

https://mcp.octoparse.com

Configure this as an MCP server endpoint, not as a REST API tool.

Authentication

The hosted server officially supports both OAuth and API key authentication:

• OAuth: the default option when the MCP client can open a browser authorization flow.
• API key: an optional authentication method for clients that can send custom HTTP headers.

For API key mode, send the key in the x-api-key header. Do not place real keys in source control, issue reports, screenshots, or shared logs.

Quick Start

Generic HTTP MCP configuration:

{
  "mcpServers": {
    "octoparse": {
      "type": "http",
      "url": "https://mcp.octoparse.com"
    }
  }
}

Claude OAuth / default authentication:

claude mcp add --transport http octoparse https://mcp.octoparse.com

Claude with API key:

claude mcp add --transport http octoparse https://mcp.octoparse.com --header "x-api-key: YOUR_API_KEY"

Codex CLI:

codex mcp add octoparse --url https://mcp.octoparse.com

Gemini CLI example configuration:

{
  "mcpServers": {
    "octoparse": {
      "httpUrl": "https://mcp.octoparse.com",
      "oauth": {
        "clientId": "Octoparse",
        "enabled": true
      }
    }
  }
}

After adding the server, complete authorization in the browser if your client prompts for OAuth.

More client examples are in Configuration.

Tools

See Tools for inputs, examples, and common failure cases.

Typical Workflow

search_templates -> execute_task -> export_data

Example user prompt:

Find a cloud-capable Octoparse template for Amazon product listings, run it for wireless earbuds, and export the result as CSV.

For an existing task, use:

search_tasks -> export_data

Scheduling, notifications, recurring jobs, and external automations are handled by the MCP client or another automation system. The MCP server exposes task and export tools; it does not provide a standalone scheduler.

Scope

Octoparse MCP Server can:

• Search the Octoparse template library.
• Create and run cloud-capable tasks from Octoparse preset templates.
• Validate template parameters before execution.
• Export collected data when a task has data available.
• Search, start, stop, monitor, and export existing cloud-supported tasks, including existing cloud-supported custom tasks.

It does not:

Shortened. The full README is on GitHub.