How can the AI agent run a scrape on a list of product URLs?

First, find your specific scraping Actor ID via `list_actors`. Then, prompt your agent to execute `run_actor`, providing the target URLs formatted as a structured JSON input payload. It returns a 'Run ID'. You can poll this run via `get_run`, and once it succeeds, the agent calls `get_dataset_items` to pull all acquired data straight to your window.

Can the agent interact with run configurations mid-way during crawling?

Yes. If an Apify crawler is currently executing and utilizes a Request Queue, you can instruct your agent to call `push_to_queue`. Doing so dynamically ships new URLs to the active queue instance, extending the current web crawl without needing to stop or restart the Actor.

Can my AI automatically detect scraping timeouts and debug the failure?

Absolutely. Because your agent can track real execution flows with `get_run`, it's aware if it transitions to TIMED-OUT or FAILED states. Subsequently, you can ask the agent to examine the KV Store log outputs ensuring the underlying issue (e.g. captcha block, blocking proxy) is identified immediately.

Apify MCP Server for Windsurf 10 tools — connect in under 2 minutes

Name: Apify
Availability: InStock
Author: Vinkius

docs.windsurf.com/windsurf/mcp

Built by Vinkius GDPR 10 Tools IDE

Windsurf brings agentic AI coding to a purpose-built IDE. Connect Apify through the Vinkius and Cascade will auto-discover every tool — ask questions, generate code, and act on live data without leaving your editor.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Apify and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "apify": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Apify MCP Server

Connect your Apify workspace to your AI agent and seamlessly direct full-stack web scraping and data extraction workflows through natural conversation.

Windsurf's Cascade agent chains multiple Apify tool calls autonomously — query data, analyze results, and generate code in a single agentic session. Paste the Vinkius Edge URL, reload, and all 10 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.

What you can do

Discover & Run Actors — Browse all scraper bots (Actors) available in your account. Fire them off asynchronously or synchronously for fast, targeted scraping
Extract Datasets — Pull robust structured data formats out of completed runs. Retrieve detailed JSON records directly into the agent's context window
Fetch Key-Value Stores — Programmatically read snapshots, cached HTML pages, or screenshots from the Apify Key-Value repositories mapped to a run
Job Control & Scalability — Stop hanging scraper jobs, queue new dynamic URLs mid-run, or inspect deep usage analytics, compute units, and webhooks limits

The Apify MCP Server exposes 10 tools through the Vinkius. Connect it to Windsurf in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Apify to Windsurf via MCP

Follow these steps to integrate the Apify MCP Server with Windsurf.

Open MCP Settings

Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"

Add the server

Paste the JSON configuration above into mcp_config.json

Save and reload

Windsurf will detect the new server automatically

Start using Apify

Open Cascade and ask: "Using Apify, help me..." — 10 tools available

Why Use Windsurf with the Apify MCP Server

Windsurf provides unique advantages when paired with Apify through the Model Context Protocol.

Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention

Purpose-built for agentic workflows — Cascade understands context across your entire codebase and integrates MCP tools natively

JSON-based configuration means zero code changes: paste a URL, reload, and all 10 tools are immediately available

Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts

Apify + Windsurf Use Cases

Practical scenarios where Windsurf combined with the Apify MCP Server delivers measurable value.

Automated code generation: ask Cascade to fetch data from Apify and generate models, types, or handlers based on real API responses

Live debugging: query Apify tools mid-session to inspect production data while debugging without leaving the editor

Documentation generation: pull schema information from Apify and have Cascade generate comprehensive API docs automatically

Rapid prototyping: combine Apify data with Cascade's code generation to scaffold entire features in minutes

Apify MCP Tools for Windsurf (10)

These 10 tools become available when you connect Apify to Windsurf via MCP:

abort_run

Any data already scraped and pushed to the dataset is preserved. The run status changes to ABORTED. Use this to stop runaway scrapes or when sufficient data has been collected. Graceful shutdown depends on the actor implementation. Abort an active Apify actor run

get_account_limits

Essential for monitoring consumption and avoiding overage charges. Check Apify account subscription limits and compute unit usage

get_dataset_items

The datasetId is found in the run object (defaultDatasetId). Supports pagination via limit (max items per page) and offset (starting position). Returns an array of JSON objects containing the scraped data fields. Use limit=1000 for bulk downloads. Export structured JSON data from an Apify dataset

get_key_value_store

Key-value stores hold arbitrary data like screenshots (OUTPUT), configuration files, or intermediate results. The storeId comes from the run object (defaultKeyValueStoreId). Common keys include "OUTPUT", "INPUT", and "SCREENSHOT". Retrieve an item from an Apify actor key-value store

get_run

Poll this endpoint to track long-running scrapes. Check the status and metadata of a specific Apify actor run

list_actors

Includes owned actors and those from the Apify Store that have been saved. Each entry contains the actorId, name, description, and default run configuration. Use the actorId to trigger runs. List all accessible actors in the Apify account

list_webhooks

RUN.SUCCEEDED, ACTOR.RUN.FAILED), target URLs, and associated actor IDs. Webhooks enable event-driven architectures by notifying external systems when actor runs complete or fail. List all configured webhooks in the Apify account

push_to_queue

Pass the queueId (from the run object) and a JSON string array of request objects, e.g., [{"url":"https://...","uniqueKey":"..."}]. This enables dynamic crawling where new pages are discovered and added during execution. Dynamically push new URLs to an active Apify request queue

run_actor

Pass the actorId (e.g., "apify/web-scraper" or a custom ID) and a JSON string with the input configuration (start URLs, proxy settings, max pages, etc.). Returns immediately with a runId. Use ap.get_run to poll for completion and ap.get_dataset_items to retrieve extracted data. Start an Apify actor asynchronously with custom JSON input

run_actor_sync

run_actor but waits for the actor to finish before returning. The response includes the full run object with defaultDatasetId for immediate data retrieval. Best for short-lived actors (under 5 minutes). For long-running scrapes, use the async ap.run_actor instead. Run an Apify actor and block until completion (synchronous)

Example Prompts for Apify in Windsurf

Ready-to-use prompts you can give your Windsurf agent to start working with Apify immediately.

"List all the Apify actors available on my account."

"Verify the status of run 'qKpwH9LgC3r0Xm' and show me its final dataset if finished."

"How are our compute usage limits tracking this current month on Apify?"

Troubleshooting Apify MCP Server with Windsurf

Common issues when connecting Apify to Windsurf through the Vinkius, and how to resolve them.

Server not connecting

Check Settings → MCP for the server status. Try toggling it off and on.

Apify + Windsurf FAQ

Common questions about integrating Apify MCP Server with Windsurf.

How does Windsurf discover MCP tools?

Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.

Can Cascade chain multiple MCP tool calls?

Yes. Cascade is an agentic system — it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.

Does Windsurf support multiple MCP servers?

Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.