Apify MCP Server for CursorGive Cursor instant access to 7 tools to Get Dataset Results, Get Run Details, List Actor Runs, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The Apify app connector for Cursor is a standout in the Friends Mcp category — giving your AI agent 7 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Apify and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"apify-extended": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 account to any AI agent and simplify how you manage your web scraping, automation actors, and data storage through natural conversation.
Cursor's Agent mode turns Apify into an in-editor superpower. Ask Cursor to generate code using live data from Apify and it fetches, processes, and writes. all in a single agentic loop. 7 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
What you can do
- Actor Control — List and trigger serverless actors for web scraping and automation directly from your agent.
- Dataset Retrieval — Fetch the resulting data records (items) from your datasets to analyze or process values via AI.
- Run Monitoring — Track the history and status of recent actor executions to ensure reliability.
- Task Management — List and query configured actor tasks to reuse saved scraper settings.
- Data Insights — Retrieve detailed metadata and logs for specific runs to debug complex automations.
- Storage Visibility — List all datasets in your account to manage your collected web data.
The Apify MCP Server exposes 7 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 7 Apify tools available for Cursor
When Cursor connects to Apify through Vinkius, your AI agent gets direct access to every tool listed below — spanning data-extraction, serverless-actors, web-automation, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Get items from a dataset
Get details for a specific run
List recent actor executions
List configured actor tasks
List Apify actors
List Apify datasets
Trigger an actor run
Connect Apify to Cursor via MCP
Follow these steps to wire Apify into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using Apify
Why Use Cursor with the Apify MCP Server
Cursor AI Code Editor provides unique advantages when paired with Apify through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Apify + Cursor Use Cases
Practical scenarios where Cursor combined with the Apify MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for Apify in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Apify immediately.
"List all actors in my Apify account."
"Run the 'Instagram Scraper' with input { "hashtags": ["#AI"] }."
"Show me the results from dataset 'ds_10293'."
Troubleshooting Apify MCP Server with Cursor
Common issues when connecting Apify to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Apify + Cursor FAQ
Common questions about integrating Apify MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.