Octoparse MCP Server

com.octoparsePublished by octoparse.comOfficial publisherv1.0.0Updated Oct 24, 2026

Official Octoparse MCP server for template discovery, cloud tasks, and structured data export.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping Data & Analytics

Server details

Identifier: com.octoparse/octoparse-mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to octoparse.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.octoparse%2Foctoparse-mcp.svg)](https://sourceweft.com/mcp/com.octoparse%2Foctoparse-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted Octoparse MCP server that lets an assistant find scraping templates, run cloud tasks, and export the collected data.

What you can do: Search Octoparse templates by keyword, template ID, or slug
Create and start cloud tasks from preset templates, with parameter validation
Search existing tasks in the account and start or stop them by task ID
Export task results as JSON, CSV, Excel, HTML, or XML once data is ready
Redeem promotion, coupon, or resource codes supplied by the user
When to use it: Useful when you want an assistant to run Octoparse's preset cloud scraping templates and pull the results into a conversation or file, for example collecting product listings and exporting them as CSV. It is not for building custom scrapers, editing task configuration, or running local-only desktop tasks.
Requirements: A remote Streamable HTTP endpoint at mcp.octoparse.com, configured as an MCP server rather than a REST tool. Authentication is required: OAuth (default, needs a browser authorization flow) or an API key sent in the x-api-key header. Cloud runs depend on account permissions and available credits or quota.

Before you install

The API key or OAuth token grants access to the Octoparse account; keep it out of source control, logs, screenshots, and shared issues, and prefer OAuth for interactive clients. Tools create and start tasks and redeem coupon codes, which changes account state and may consume credits or quota. Data is collected from third-party sites and exported through Octoparse's hosted service.

Installation

In SourceWeft

Open Octoparse MCP Server in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.octoparse%2Foctoparse-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

Octoparse MCP Server

[Octoparse] [Docs] [MCP]

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:

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:

json

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

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

Claude OAuth / default authentication:

Claude with API key:

bash

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

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

Codex CLI:

Gemini CLI example configuration:

json

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

{  "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

Tool	Purpose
`search_templates`	Find Octoparse templates by keyword, template ID, or slug.
`execute_task`	Validate parameters, create a cloud task from an Octoparse preset template, and start extraction.
`export_data`	Export task results as JSON, CSV, Excel, HTML, or XML when data is ready.
`search_tasks`	Search existing tasks in the authenticated account.
`start_or_stop_task`	Start or stop an existing cloud task by task ID.
`redeem_coupon_code`	Redeem a promotion, coupon, or resource code supplied by the user.

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

Typical Workflow

Example user prompt:

text

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

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:

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:

Run local-only desktop tasks through the hosted server.
Create fully custom scraping tasks.
Create or edit custom task configuration details such as custom fields, pagination rules, loop logic, browser workflow, or extraction steps.
Upload private templates.
Provide billing or account administration tools.
Schedule recurring runs by itself.

Common Limits

Some templates are local-only and must be run in the Octoparse desktop app.
Cloud execution depends on account permissions, available credits or quota, target-site availability, and template support.
Long-running tasks may need follow-up calls. If data is still collecting or exporting, wait and call export_data again.
Tool availability can be narrowed with includeTools or excludeTools URL parameters. See Overview.

Security

Keep API keys and OAuth tokens out of Git, logs, screenshots, and public issues.
Use OAuth when possible for interactive clients.
Use x-api-key only with clients that store headers securely.
Report vulnerabilities privately. See Security.

Documentation

Development

For local environment variables, copy .env.example to .env and fill only values needed for your environment. Never commit .env.

Contributing

Contributions are welcome. Please read CONTRIBUTING.md before opening issues or pull requests.

License

MIT. See LICENSE.md.

Source: README.md at commit 3906b5e

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts