Zyte MCP is a remote MCP server that lets an agent use Zyte on your behalf. It can download pages with a plain HTTP request or in a real browser, click and type and take screenshots, and pull structured data out of a page with AI, either as a standard type like product, article or job posting or as fields you describe in plain words. It can also search the web from a chosen country, check whether Zyte API supports a site and what a request costs, and report your usage by domain.
If you have Scrapy Cloud projects, the same server can list spiders, start and cancel jobs, read logs and items, manage schedules and settings, and read and write collections. Those tools can change and delete things, so review what your agent asks to do.
Connect to https://mcp.zyte.com/v1/mcp and sign in to your Zyte account with OAuth. Using the server is free. What your agent does through it is billed at Zyte API prices, on a dedicated mcp_access_key you can track and cap. New accounts get $5 of trial credit for a month.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 34 tools
The four fetch/extract tools are clearly differentiated by browser vs HTTP and raw vs structured, with explicit cross-references in their descriptions. Each Scrapy Cloud tool targets a distinct resource and operation, so no two tools appear to do the same thing.
All tools use snake_case, and the scrapy_cloud_* prefix is applied consistently across 26 tools. The remaining tools mix patterns like extract_from_X, fetch_X, and bare names such as search and user_info, which slightly reduces predictability.
34 tools is heavy, but the server spans two distinct product surfaces (Zyte API and Scrapy Cloud) with many resources requiring full CRUD. The count is large yet mostly warranted by the breadth of the domain.
Scrapy Cloud coverage is thorough across jobs, projects, spiders, collections, periodic jobs, and settings, and Zyte API covers extraction, fetching, search, pricing, and usage. Minor gaps include no spider deployment or project creation, but the surface is otherwise complete.
Web scraping, extraction and search for AI agents. Hosted MCP with workspace API keys.
Zyte API MCP — unified web fetch + AI extraction (zyte.com)
Your agent needs the open web — searched by more than one engine, and read as clean markdown rather than raw HTML. **What you can ask for** • "Search this question with two providers and tell me where they disagree." • "Scrape these 40 URLs into markdown, in one batch." • "Crawl this documentation site and give me every page." • "Do deep research on this topic and cite the sources." • "Find the academic papers behind this claim." **How to use it** Point any MCP client at https://mcp.aisa.one/search/mcp and sign in with OAuth — there is no key to create or paste. 30 tools across several independent providers: Tavily and Exa search, answers, contents and agent runs; Firecrawl scrape, batch scrape, crawl, map and search; Perplexity Sonar, Sonar Pro, reasoning and deep research; Oxylabs AI search and LLM jobs; OpenAI and Anthropic web search; and scholarly search. **Why this rather than the source** Several independent indexes behind one account, because one engine's blind spot is not visible from inside it. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the page here, then ask the same agent who links to it or how much traffic it gets — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo-serp/mcp for the Google results page itself, https://mcp.aisa.one/seo-serp-other-engines/mcp for Bing, Baidu and Naver.
Your agent needs marketplace data — what a product costs on Amazon and Google Shopping, who the sellers are, what reviewers actually complain about. **What you can ask for** • "What is this ASIN's price history, rating and seller list?" • "Who else sells this product, and at what price?" • "Pull the reviews for this product and group the complaints." • "What comes up on Google Shopping for this query in the UK?" • "Compare these products across both marketplaces." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-merchant/mcp and sign in with OAuth — there is no key to create or paste. 22 tools: Amazon products, ASIN detail and sellers; Google Shopping products, product info, sellers and reviews; live and queued forms, with raw HTML where you need it. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Price the product here, then ask the same agent what the brand's site traffic or ad spend looks like — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Add one secure layer between your agents and this server.
