🔜 An official Octoparse Claude connector is coming soon
Before You Begin
Please review the following before getting started:
✅ Claude supports custom connectors using remote MCP in beta.
✅ For Pro / Max users, you can add a custom connector directly in Settings > Connectors.
✅ For Team / Enterprise, an Owner must first add the connector at the organization level before individual members can connect it.
✅ Free users can use custom connectors too, but are limited to one custom connector.
What This Integration Enables
Once Octoparse is connected to Claude, you can manage scraping workflows in natural language, including:
Search Octoparse scraping templates
Create scraping tasks from templates
Start and stop cloud tasks
Check task execution status
Export data in CSV or JSON
View Octoparse account information
Octoparse MCP Server Information
Octoparse provides an MCP server that Claude can connect to through Claude’s custom connector framework.
Server URL
https://mcp.octoparse.com
This server securely exposes Octoparse capabilities—such as templates, tasks, and exports—to Claude through the MCP standard.
Step-by-step configuration
Follow these steps to connect Octoparse with Claude.
Step 1: Open Claude Settings
Log in to your Claude account.
Open Settings in Claude.
Then navigate to Connectors. Claude’s official help center documents this as the place where Pro and Max users add custom connectors, and where users enable configured connectors.
Step 2: Add a Custom Connector
In the Connectors section:
Click Add custom connector
Enter the Octoparse MCP server URL:
https://mcp.octoparse.com
Claude’s official support docs say Pro / Max users can add a remote MCP server from Settings > Connectors, and optionally open Advanced settings to specify an OAuth Client ID and Client Secret when needed.
Step 3: Configure Authentication
If prompted for authentication settings:
Use OAuth
If Octoparse supports dynamic client registration, you may not need to manually fill in Client ID / Client Secret
If your server requires fixed OAuth credentials, you can enter them in Advanced settings
Claude officially supports both authless and OAuth-based remote MCP servers, and supports dynamic client registration as well as manually specified client credentials in supported cases.
Step 4: Finish Adding the Connector
Click Add to save the connector.
Once it is configured, Octoparse will appear in your available connectors list.
For Team / Enterprise workspaces, note that only Owners can add the connector initially. After that, members can find it in their connectors list and click Connect to authenticate.
Step 5: Authorize Access with Octoparse
When you connect or first use the Octoparse connector, Claude will typically start an OAuth flow:
A browser window opens
You sign in to your Octoparse account
You review the requested permissions
You approve access
Claude’s help center states that when using OAuth-based custom connectors, users typically authenticate through OAuth and Claude never sees the actual password.
Step 6: Enable the Connector in a Conversation
After the connector is configured, you can enable it for a specific chat.
Claude’s current workflow allows connectors to be enabled per conversation through the “+” button in the lower-left of the chat interface, then Connectors, where you can toggle connectors on or off for that conversation.
Authentication (OAuth)
When you use Octoparse tools in Claude for the first time:
Claude attempts to call an Octoparse tool
You may be redirected to Octoparse for login and authorization
You approve the requested permissions
Authorization completes via OAuth
🔐 Claude does not have access to your Octoparse password. OAuth grants scoped access securely instead.
Example Claude Prompts (After Integration)
Template & Task Creation
Find a template for scraping Amazon product listings. Create a task using that template and start it in the cloud.
Monitoring & Export
Check the status of my latest Octoparse cloud task and export the results as CSV.
Data Retrieval
Show me all available export options for this Octoparse task and download the latest dataset in JSON format.
Important Usage Notes
✅ Only workflows supported by your Octoparse account and plan can be executed successfully.
✅ Claude custom connectors can expose tools that read data or take actions, depending on how the MCP server is built. Anthropic specifically warns that custom connectors can read, create, modify, or delete data depending on granted permissions, so users should review permissions carefully.
⚠️ Cloud execution may consume Octoparse credits, depending on your task type and plan.
⚠️ Some Octoparse templates or capabilities may require higher-tier plans.
⚠️ Only connect Claude to MCP servers you trust. Anthropic explicitly warns that remote MCP servers are third-party services and should be reviewed carefully before connecting.
Team / Enterprise Note
If you are using Claude Team or Enterprise:
The workspace Owner must first add the Octoparse connector in Organization settings > Connectors
Individual users then connect and authorize it for their own account access
This is the official Claude flow for Team / Enterprise custom connectors.
Mobile / Desktop Note
Anthropic’s current documentation says remote MCP servers are supported on Claude and Claude Desktop, and that Claude for iOS and Android can use remote servers that were already added via claude.ai, although users cannot add new servers directly from mobile.
What’s Coming Next 🚀
✅ Easier custom connector setup in Claude
✅ Improved permissions and admin controls
✅ Better multi-device connector support
✅ Smoother AI-driven workflow automation with Octoparse

