Back to Browse

Rossai Apify MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (4 strong, 3 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

8 files analyzed · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

file_system

Check that this permission is expected for this type of plugin.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

What You'll Need

Set these up before or after installing:

Your own Apify API token. This package does not include one.Required

Environment variable: APIFY_TOKEN

Documentation

View on GitHub

From the project's GitHub 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

npm install
npm run build
APIFY_TOKEN=your_token node dist/index.js

Claude Desktop and other stdio clients can use:

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

Streamable HTTP

npm run build
APIFY_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

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.

Reviews

No reviews yet

Be the first to review this server!