22nd of 12 in MCP servers

apify-mcp-server

Official MCP server exposing Apify Store Actors as tools for web scraping

Stars
15.7k
License
MIT
Last commit
Nov 2026
Last release
Nov 2026
Language
TypeScript
Stars, last 29 weeks+14,570
21 Apr 2026: 1,150 stars28 Apr 2026: 1,185 stars5 May 2026: 1,210 stars12 May 2026: 1,230 stars19 May 2026: 1,261 stars26 May 2026: 1,296 stars2 Jun 2026: 1,319 stars9 Jun 2026: 1,339 stars16 Jun 2026: 1,362 stars23 Jun 2026: 1,391 stars30 Jun 2026: 1,495 stars7 Jul 2026: 1,726 stars14 Jul 2026: 1,925 stars21 Jul 2026: 2,134 stars28 Jul 2026: 2,335 stars4 Aug 2026: 2,555 stars11 Aug 2026: 3,293 stars18 Aug 2026: 4,114 stars25 Aug 2026: 4,904 stars1 Sept 2026: 5,607 stars8 Sept 2026: 6,376 stars15 Sept 2026: 7,250 stars22 Sept 2026: 8,057 stars29 Sept 2026: 8,977 stars6 Oct 2026: 9,881 stars13 Oct 2026: 11,062 stars20 Oct 2026: 12,297 stars27 Oct 2026: 13,526 stars3 Nov 2026: 14,647 stars10 Nov 2026: 15,720 stars

1,150 on 21 Apr 202615,720 on 10 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

MCP server that lets an agent search Apify Store, read an Actor's input schema and pricing, run it, and fetch results from its dataset. It runs hosted at mcp.apify.com over Streamable HTTP with OAuth or a bearer token, or locally over stdio via the @apify/actors-mcp-server npm package. Actors execute on the Apify platform in both modes.

Who it is for: Agent builders who need web scraping and data extraction tools over MCP

Strengths

  • One connection reaches thousands of Store Actors instead of a separate MCP server per site
  • Tool categories selectable via `tools` URL parameter, `--tools` flag or `TOOLS` env var
  • Hosted OAuth endpoint plus local stdio mode and an .mcpb bundle for supported clients
  • Also covers Actor builds, schedules, tasks, storage and Apify API access as opt-in tools

Weaknesses

  • Requires an Apify account; Actors run and store results on Apify's platform, not locally
  • Actor runs are paid per Actor pricing; cost depends on each Actor
  • call-actor waits only 30 seconds by default, up to 45; longer runs need polling
  • Local stdio mode lacks inferred output schemas for Actor results

What it needs

  • no GPU
  • Docker
  • Needs Apify account and API token or OAuth, Apify platform (Actors), Node.js 22+ for local stdio

Quick answers

Is apify-mcp-server open source?

Yes. Its code is on GitHub under the MIT license.

Can you run apify-mcp-server with Docker?

Yes. Its repository has a Docker setup: a Dockerfile, a Compose file or a published image.

Does apify-mcp-server need a GPU?

No, it runs without one.

Head to head

Also in MCP servers

See all 12
Also in MCP servers
RankProjectScore
1serversReference MCP servers for files, git, fetch, memory and time91.9k starscustom license94 out of 100
3xiaohongshu-mcpMCP server that lets AI clients post, search and comment on Xiaohongshu17.1k stars+912 (+5.6%) in 30 daysApache-2.085 out of 100
#4ha-mcpMCP server that lets AI assistants configure and control Home Assistant7.1k starsMIT80 out of 100
#5mcp-atlassianMCP server exposing Jira and Confluence tools to AI assistants6.1k stars+140 (+2.3%) in 30 daysMIT69 out of 100
#6figma-console-mcpMCP server that reads and writes Figma files, variables and components3.3k stars+819 (+33%) in 30 daysMIT68 out of 100