← All tools

Research infrastructure · MCP

Give your agent the web it can’t reliably reach.

Decodo turns difficult public web pages into structured inputs an AI agent can actually use—then exposes the workflow through an official MCP server.

Partner link. It supports Superbash Learn at no extra cost to you.

Hand-cut paper diagram of a web page moving through a Decodo MCP bridge into an AI agent and a verified research table.
Page retrieval → MCP tool → agent reasoning → checked deliverable

Search finds the page. Decodo helps the agent finish the job.

Use it when your workflow needs complete page content, repeatable fields, a visual capture, or a target-specific scraper—not just a list of search snippets. The useful pattern is simple: let Decodo retrieve the evidence, let the agent interpret it, and make a human review the final result.

Three jobs where it changes the outcome

01

Pages that resist ordinary browsing

Retrieve a public page as clean Markdown or capture a truthful screenshot when JavaScript, layout, or anti-bot friction gets in the way.

scrape_as_markdown · screenshot
02

Marketplace research

Compare products, prices, sellers, and availability across structured ecommerce targets without asking the model to guess from snippets.

Amazon · Walmart · Target
03

Search and social evidence

Collect current results from search engines, Reddit, YouTube, or TikTok, then make the agent cite and review what it found.

Search · Reddit · YouTube · TikTok

Connect narrowly. Test cheaply. Scale only what works.

Decodo’s current MCP documentation supports a hosted endpoint as well as its official npm server. The exact client configuration differs, but the operating discipline should not.

  1. 01

    Get the right token

    Create a Decodo Web Scraping API account and copy its Basic authentication token. Keep it in your client’s secret or environment configuration—never in a prompt or repository.

  2. 02

    Connect the official MCP server

    Use the local @decodo/mcp-server package or the hosted endpoint at https://mcp.decodo.com/mcp. Follow your agent client’s MCP configuration format.

  3. 03

    Expose only the tools you need

    Start with web plus one job-specific toolset such as search, ecommerce, or social_media. A smaller catalog makes tool choice easier to audit.

  4. 04

    Run one bounded test

    Name the target, required fields, failure behavior, and maximum request count. Verify the source URLs and output before turning the prompt into a repeatable workflow.

Make the budget and evidence rules explicit.

Use Decodo's scrape_as_markdown tool on [PUBLIC URL].
Return: title, source URL, date, and five evidence-backed findings.
If the page fails, stop after one retry and report the error.
Cap the entire run at 2 Decodo requests.

Build the full Hermes + Decodo workflow

Our complete tutorial covers local and hosted MCP configuration, token handling, a safer Amazon comparison, request budgets, troubleshooting, and when to wrap the process in a reusable Hermes Skill.