Ross AI Apify Actors

io.github.rossbuildsPublished by GitHub account rossbuildsv1.0.0Updated Oct 30, 2026

Run Ross AI Apify actors with your own token. Sitemap, SEO, Trends, screenshots, reviews, Markdown.

The publisher's own server: Apify MCP Server

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Runs six public Apify actors (sitemap extraction, SEO audit, Google Trends, screenshots, app reviews, PDF/URL to Markdown) using your own Apify token.

What you can do
  • Extract URLs from a site's sitemap
  • Run an SEO and AI search readiness audit on a site
  • Scrape Google Trends data in batches
  • Capture website screenshots in batches
  • Collect iOS and Android app reviews
  • Convert a URL or PDF into Markdown
When to use it
Useful when you want an assistant to gather web research data — sitemaps, SEO checks, trend data, screenshots, app reviews or page-to-Markdown conversion — through ready-made Apify actors without writing your own scrapers.
Requirements
Runs locally as a Node.js stdio process (npm install and build, or the .mcpb bundle, or Docker). Requires your own Apify API token in the APIFY_TOKEN environment variable. Network access to the Apify API. Optional HTTP mode listens on 127.0.0.1:8787, configurable with PORT.
Before you install
Requires your personal Apify API token, which the package does not include; the bundle asks for it at install time. Actor runs consume your Apify account credits, so usage may cost money. Tools send target URLs and queries to Apify's hosted actors. Runs are capped at 300 seconds of waiting and 100 returned items.

Installation

In SourceWeft

  1. Open Ross AI Apify Actors in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

rossai-apify-mcp

[Listed on mcpservers.org]

MCP server for the public Apify actors published by appreciative_duct. Each tool starts an Actor run with the Apify API and returns the dataset items.

The server reads APIFY_TOKEN from the environment. That token has to be yours. Nothing in this package embeds one.

Tools

ToolActor
sitemap-url-extractorSitemap URL Extractor
seo-audit-ai-search-readinessSEO Audit & AI Search Readiness
google-trends-batch-scraperGoogle Trends Scraper (Batch, Reliable)
website-screenshot-batchWebsite Screenshot Batch
app-reviews-ios-androidApp Reviews for iOS and Android
url-pdf-to-markdownURL and PDF to Markdown

A tool waits up to waitSeconds (default 180, maximum 300) and returns at most 100 dataset items. The response includes the run id and the Console URL when there is more to open.

stdio

bash
npm installnpm run buildAPIFY_TOKEN=your_token node dist/index.js

Claude Desktop and other stdio clients can use:

json
{  "mcpServers": {    "rossai-apify": {      "command": "node",      "args": ["/absolute/path/to/rossai-apify-mcp/dist/index.js"],      "env": { "APIFY_TOKEN": "your_token" }    }  }}

Streamable HTTP

bash
npm run buildAPIFY_TOKEN=your_token node dist/index.js --http

The server listens on http://127.0.0.1:8787/mcp. Set PORT to change it. GET /health returns { "ok": true }.

Zero-install Apify MCP

Apify hosts an MCP endpoint that can call these actors without this package. Your Apify token is still required by that host:

https://mcp.apify.com/?actors=appreciative_duct/sitemap-url-extractor,appreciative_duct/seo-audit-ai-search-readiness,appreciative_duct/google-trends-batch-scraper,appreciative_duct/website-screenshot-batch,appreciative_duct/app-reviews-ios-android,appreciative_duct/url-pdf-to-markdown

Registry files

server.json names the server io.github.rossbuilds/rossai-apify-mcp in the official MCP registry and points at the .mcpb bundle attached to the GitHub release v1.0.0. glama.json lists the maintainer. mcpb/manifest.json is the bundle manifest. The bundle asks for your token at install time. youtube-transcript-batch is not a tool here because that actor stayed private.

Source

https://github.com/rossbuilds/rossai-apify-mcp

Docker

bash
docker build -t rossai-apify-mcp .docker run -i --rm -e APIFY_TOKEN rossai-apify-mcp

The image runs the stdio server as the non-root node user. No token is baked in; pass APIFY_TOKEN at runtime.

Source: README.md at commit 8e95d4c

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v1.0.0LatestOct 22, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Apify integrations