Apify MCP Server connects AI agents to Apify's collection of web scrapers, crawlers, and automation tools through the Model Context Protocol, allowing them to extract data from websites, search engines, social media, maps, and online stores. It is for users who want agents to collect web data through compatible clients such as Claude Code, Claude.ai, Cursor, or VS Code. The catalogue entries configure or extend agent use of this MCP server.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/apify/apify-mcp-server/storybookgit clone --depth 1 https://github.com/apify/apify-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/apify/apify-mcp-server/storybook)<a href="https://agentmods.dev/mcp/apify/apify-mcp-server/storybook"><img src="https://agentmods.dev/badge/mcp/apify/apify-mcp-server/storybook.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
storybook scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"storybook": {
"type": "http",
"url": "https://baldasseva--storybook-mcp.apify.actor/mcp?token=${APIFY_TOKEN}"
}
}What else .mcp.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 6 lines scan A 1993fbdbc3c5
storybook is an MCP server published in the GitHub repository apify/apify-mcp-server (5,848 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
strata
MCP server for progressive tool usage at any scale (see https://klavis.ai). Remote server at strata.klavis.ai.
pare-test
Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON. Runs locally from the @paretools/test npm package.
claude-octopus
Spawn multiple specialized Claude Code agents as MCP servers, each independently configured. Runs locally from the claude-octopus npm package. Needs 7 environment variables to run.
mcp-pve
Manage Proxmox VE through AI assistants. Runs locally from the @samik081/mcp-pve npm package. Needs 3 environment variables to run.
transcriptor-mcp
MCP server "transcriptor-mcp" as configured in samson-art/transcriptor-mcp. Runs in Docker (docker.io/artsamsonov/transcriptor-mcp:1.2.4).
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.