How to integrate Scrape do MCP with Codex

GET STARTED FOR FREE
Scrape do logo
Codex logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Scrape do MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Scrape do with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Scrape do MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on connect.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

What is the Scrape do MCP server, and what's possible with it?

The Scrape do MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Scrape do account. It provides structured and secure access to robust web scraping tools, so your agent can perform actions like scraping dynamic pages, managing sessions, setting custom headers or proxies, and extracting structured data from any website on your behalf.

  • Dynamic page scraping with headless browsers: Retrieve fully rendered HTML content from JavaScript-heavy or protected websites by leveraging advanced browser emulation and proxy rotation.
  • Custom scraping session management: Set device type, cookies, wait times, and custom headers to imitate different users, maintain sessions, or access device-specific content for tailored data extraction.
  • Proxy and anti-bot bypass control: Enable super or proxy modes to utilize residential, mobile, or datacenter proxies, helping your agent bypass strict anti-bot systems and geo-restrictions seamlessly.
  • Targeted resource filtering: Block specific URLs like ads or analytics scripts during scraping to increase speed, avoid distractions, and improve privacy.
  • Account usage and statistics retrieval: Access real-time usage stats, subscription status, and remaining request limits so your agent can monitor scraping quotas and avoid interruptions.

Supported Tools & Triggers

Tools
Get Account InformationRetrieves account information and usage statistics from scrape.
Get rendered page contentThis tool allows you to scrape web pages with javascript rendering enabled.
Scrape webpage using scrape.doA tool to scrape web pages using scrape.
Use Scrape.do Proxy ModeThis tool implements the proxy mode functionality of scrape.
Set Cookies for ScrapingThis tool allows users to set specific cookies for their scraping requests to a target website.
Set Scrape.do Super ModeThe scrape do set super mode tool enables enhanced scraping by using residential and mobile proxies, bypassing blocks and restrictions associated with datacenter ips.
Block specific URLs during scrapingThis tool allows users to block specific urls during the scraping process.
Set custom headers for scrape.do requestA tool to send custom headers with scrape.
Set Custom Wait TimeThis tool sets the custom wait time in milliseconds after page load when using the render option in scrape.
Set Device Type for ScrapingThis tool allows users to set the device type (desktop, mobile, or tablet) for making scraping requests.
Set Disable RedirectionControls the automatic redirection behavior of scrape.
Set Pure Cookies ModeThis tool enables getting the original set-cookie headers from target websites instead of the processed scrape.
Set Regional Geolocation for ScrapingThis tool allows users to set a broader geographical targeting by specifying a region code instead of a specific country code.
Set Retry TimeoutThis tool allows users to set the maximum wait time (in milliseconds) before retrying a failed request in scrape.
Set Screenshot Capture for ScrapingThis tool enables the screenshot functionality for the scrape.
Set Session ID for Sticky SessionsThis tool implements the session id functionality for scrape.
Set Wait For SelectorThis action allows setting a css selector to wait for before considering the page load complete.
Set Wait Until ConditionThis tool sets the waituntil parameter for the scrape.
Monitor WebSocket requests using scrape.doThis tool provides the ability to view websocket requests made by a webpage.

Conclusion

You've successfully integrated Scrape do with Codex using Composio's MCP server. Now you can interact with Scrape do directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Scrape do operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Scrape do operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Scrape do MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Scrape do MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Scrape do MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Scrape do MCP with Claude Code

OpenClaw logo

OpenClaw

Use Scrape do MCP with OpenClaw

CLI logo

CLI

Use Scrape do MCP with CLI

Google ADK logo

Google ADK

Use Scrape do MCP with Google ADK

LangChain logo

LangChain

Use Scrape do MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Scrape do MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Scrape do MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Scrape do MCP with LlamaIndex

CrewAI logo

CrewAI

Use Scrape do MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Scrape do MCP?

With a standalone Scrape do MCP server, the agents and LLMs can only access a fixed set of Scrape do tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Scrape do and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Codex?

Yes, you can. Codex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Scrape do tools.

Can I manage the permissions and scopes for Scrape do while using Tool Router?

Yes, absolutely. You can configure which Scrape do scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Scrape do data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free