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.
Borrowing it
Nothing to install: this file belongs to apify/apify-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/apify/apify-mcp-server/master/AGENTS.mdgit 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/instructions/apify/apify-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/apify/apify-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/apify/apify-mcp-server/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/apify/apify-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/apify/apify-mcp-server/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02625 | $0.02625 |
| Opus 5.5 | $0.01050 | $0.01050 |
| Sonnet 5.5 | $0.00525 | $0.00525 |
| Haiku 4.5 | $0.00263 | $0.00263 |
Grade A, and why
apify-mcp-server AGENTS.md scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
When the user says "test with mcpc", **use mcpc** — do not invent a substitute (no curl, no ad-hoc Node/Python scripts, no unit tests in place of an e2e probe). Use the **apify CLI** (`apify datasets`, `apify key-value-s How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apify MCP server
TypeScript, ES modules. Runs in two modes: stdio (local CLI clients, stdio.ts) and HTTP Streamable (dev_server.ts).
Before implementing: work from an issue that is assigned or explicitly agreed. An open issue is not an invitation — many are stale or unrefined, and the fix isn't settled. If nobody asked for this change, open an issue instead of a PR (docs fixes excepted). Disclose AI use in the PR. See CONTRIBUTING.md.
Communication style — MANDATORY
This applies to ALL written output: code comments, commit messages, PR descriptions, issue specs
- Plain language, no fluff. Say what you mean in the fewest words. No filler phrases, no motivational preambles, no "this will improve the developer experience."
Scope discipline
- Minimal. Implement only what's explicitly requested. No speculative features, no hypothetical future-proofing — solve the current problem, not imagined ones.
- One thing per change. Bug fix fixes only the bug — no cleanup, no renames, no drive-by refactors. Mention unrelated issues; don't fix them.
- Test first for bug fixes. Write a failing test that reproduces the bug, confirm it fails, then fix.
- Refactoring is a separate PR. If a feature needs refactoring, land the refactor first, then the feature. Never mix.
- Fix by adjusting, not adding. Prefer a 1-line fix over a 10-line fix. Prefer adjusting existing code over adding new branches. Search for existing helpers and patterns that already handle similar cases. Ask: "Am I adding code, or fixing the code that's already there?"
- Self-review your diff. Before declaring done, review: Is this the minimal fix? Am I reusing existing patterns? Did I leave any debug artifacts?
Git: branch names, commits, PR titles
Conventional Commits for all three. Branch: type/short-desc (e.g. fix/connection-timeout). Commit/PR title: type: Description (e.g. fix: Handle connection errors). Types: feat, fix, chore, refactor, docs, test. Append ! for breaking changes. PR title ≤70 chars.
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.
- 9d ago Changed · +3 lines · +182 tokens per session c03b28634016
- 14d ago Changed · +4 lines · +62 tokens per session 8135a6fb13b8
- 15d ago Changed · +32 tokens per session 07a3c0690882
- 19d ago Changed · +2 tokens per session ba15d19376e7
- 2mo ago First seen · 96 lines · 2,347 tokens per session scan A 58747f84ade5
apify-mcp-server AGENTS.md is an instructions file published in the GitHub repository apify/apify-mcp-server (13,682 stars, last pushed today), licensed MIT. It adds 2,625 tokens to every session, about $0.0105 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.