Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-decodo scrape the headlines from https://news.ycombinator.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Decodo MCP — wraps the Decodo Web Scraping API (decodo.com, formerly
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tool | Description |
| Scrape any web page through Decodo (formerly Smartproxy) rotating proxies and return its content. Handles anti-bot pages; use render_js:true for JavaScript-heavy sites (headless-browser rendering) and markdown:true for clean LLM-ready markdown instead of raw HTML. BYOK — _apiKey is your Decodo Web Scraping API "username:password" credentials. Example: decodo_scrape({ url: "https://example.com", render_js: true, _apiKey: "user:pass" }) |
| Google search results scraping via Decodo (formerly Smartproxy) — runs a Google search through rotating proxies and returns structured organic results (position, title, url, snippet) plus related searches when parsing succeeds. BYOK — _apiKey is your Decodo Web Scraping API "username:password" credentials. Example: decodo_google_search({ query: "best running shoes 2026", geo: "United States", _apiKey: "user:pass" }) |
| Get structured Amazon product data via Decodo (formerly Smartproxy) — title, pricing, rating, reviews, images, availability — parsed into JSON. Pass either a full Amazon product URL or an ASIN. BYOK — _apiKey is your Decodo Web Scraping API "username:password" credentials. Example: decodo_amazon_product({ asin: "B09H74FXNW", _apiKey: "user:pass" }) |
Related MCP server: ScrapeAPI MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"decodo": {
"url": "https://gateway.pipeworx.io/decodo/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/decodo/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Decodo data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Scrape, crawl and search the web for AI agents via MCP.
Web MCP: scrape/crawl sites, web search, brand assets, app stores, YouTube, Reddit, Hacker News.
Web scraping for AI agents. Extract text and metadata from any URL worldwide. $0.005/page.
Web search, browser automation, scraping, crawling and CAPTCHA solving for AI agents.
