2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 10 Tools IDE

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Apify through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "apify": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Apify
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.

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Apify tool calls without waiting for prompts between steps. Connect 10 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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 Cline 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 Cline via MCP

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

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel

02

Add remote server

Click "Add MCP Server" and paste the configuration above

03

Enable the server

Toggle the server switch to ON

04

Start using Apify

Ask Cline: "Using Apify, help me...". 10 tools available

Why Use Cline with the Apify MCP Server

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

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Apify + Cline Use Cases

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

01

Autonomous feature building: tell Cline to fetch data from Apify and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Apify tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Apify and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Apify for real-time status and let Cline generate hotfix patches based on the findings

Apify MCP Tools for Cline (10)

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

01

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

02

get_account_limits

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

03

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

04

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

05

get_run

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

06

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

07

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

08

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

09

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

10

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 Cline

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

01

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

02

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

03

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

Troubleshooting Apify MCP Server with Cline

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

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Apify + Cline FAQ

Common questions about integrating Apify MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Connect Apify to Cline

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.