Skip to main content
If the MCP server is connected but does not behave as expected, use the checks below to identify the most common setup, authorization, and task-related issues.
The client may have cached the tool list before authorization completed. Disconnect, reconnect, and restart your client if needed.Also confirm that the server URL is exactly https://mcp.octoparse.com with no trailing slash.
OAuth success only means authentication passed. The token may have expired, or your account may not have the required permission.Try disconnecting and reconnecting to refresh the token. If the error mentions permissions, check your Octoparse plan.
The most common cause is that the selected template supports local execution only. In that case, run it from the Octoparse desktop client instead.Another common cause is insufficient cloud run credits on your account.
Check two things:
  1. Whether the task has actually finished. Use search_tasks to confirm its status.
  2. Whether your account has permission to access that task’s data.
If the task is still running, wait until it completes before calling export_data.
Close the browser tab and retry the connection flow from your MCP client.If the issue persists, clear cookies for octoparse.com and try again.