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 OpenAI Agents SDK 10 tools — connect in under 2 minutes

Name: Apify
Availability: InStock
Author: Vinkius

openai.github.io/openai-agents-python/mcp

Built by Vinkius GDPR 10 Tools SDK

The OpenAI Agents SDK enables production-grade agent workflows in Python. Connect Apify through the Vinkius and your agents gain typed, auto-discovered tools with built-in guardrails — no manual schema definitions required.

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.

python

import asyncio
from agents import Agent, Runner
from agents.mcp import MCPServerStreamableHttp

async def main():
    # Your Vinkius token — get it at cloud.vinkius.com
    async with MCPServerStreamableHttp(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ) as mcp_server:

        agent = Agent(
            name="Apify Assistant",
            instructions=(
                "You help users interact with Apify. "
                "You have access to 10 tools."
            ),
            mcp_servers=[mcp_server],
        )

        result = await Runner.run(
            agent, "List all available tools from Apify"
        )
        print(result.final_output)

asyncio.run(main())

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.

The OpenAI Agents SDK auto-discovers all 10 tools from Apify through native MCP integration. Build agents with built-in guardrails, tracing, and handoff patterns — chain multiple agents where one queries Apify, another analyzes results, and a third generates reports, all orchestrated through the Vinkius.

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 OpenAI Agents SDK 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 OpenAI Agents SDK via MCP

Follow these steps to integrate the Apify MCP Server with OpenAI Agents SDK.

Install the SDK

Run pip install openai-agents in your Python environment

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Run the script

Save the code above and run it: python agent.py

Explore tools

The agent will automatically discover 10 tools from Apify

Why Use OpenAI Agents SDK with the Apify MCP Server

OpenAI Agents SDK provides unique advantages when paired with Apify through the Model Context Protocol.

Native MCP integration via `MCPServerSse` — pass the URL and the SDK auto-discovers all tools with full type safety

Built-in guardrails, tracing, and handoff patterns let you build production-grade agents without reinventing safety infrastructure

Lightweight and composable: chain multiple agents and MCP servers in a single pipeline with minimal boilerplate

First-party OpenAI support ensures optimal compatibility with GPT models for tool calling and structured output

Apify + OpenAI Agents SDK Use Cases

Practical scenarios where OpenAI Agents SDK combined with the Apify MCP Server delivers measurable value.

Automated workflows: build agents that query Apify, process the data, and trigger follow-up actions autonomously

Multi-agent orchestration: create specialist agents — one queries Apify, another analyzes results, a third generates reports

Data enrichment pipelines: stream data through Apify tools and transform it with OpenAI models in a single async loop

Customer support bots: agents query Apify to resolve tickets, look up records, and update statuses without human intervention

Apify MCP Tools for OpenAI Agents SDK (10)

These 10 tools become available when you connect Apify to OpenAI Agents SDK 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 OpenAI Agents SDK

Ready-to-use prompts you can give your OpenAI Agents SDK 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 OpenAI Agents SDK

Common issues when connecting Apify to OpenAI Agents SDK through the Vinkius, and how to resolve them.

MCPServerStreamableHttp not found

Ensure you have the latest version: pip install --upgrade openai-agents

Agent not calling tools

Make sure your prompt explicitly references the task the tools can help with.

Apify + OpenAI Agents SDK FAQ

Common questions about integrating Apify MCP Server with OpenAI Agents SDK.

How does the OpenAI Agents SDK connect to MCP?

Use MCPServerSse(url=...) to create a server connection. The SDK auto-discovers all tools and makes them available to your agent with full type information.