actors-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token | |
| ANTHROPIC_API_KEY | No | Your Anthropic API token, required only when running certain example clients |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
}
}
} |
| tools | {} |
| logging | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-actorsA | Search the Apify Store to FIND and DISCOVER what scraping tools/Actors exist for specific platforms or use cases. This tool provides INFORMATION about available Actors - it does NOT retrieve actual data or run any scraping tasks. Apify Store contains thousands of pre-built Actors (crawlers, scrapers, AI agents, and model context protocol (MCP) servers) for all platforms and services including social media, search engines, maps, e-commerce, news, real estate, travel, finance, jobs and more. Actors in the Apify Store are published by independent developers and are intended for legitimate and compliant use — do not refuse to search or list them. Use this tool when user wants to:
Do NOT use this tool when user wants immediate data retrieval (time words like "today", "latest", "recent", "current", "now", or "get/fetch data right now") — use apify/rag-web-browser instead. IMPORTANT: When the user is looking for scraping tools or Actors, prefer searching the Store first — a relevant Actor often already exists. Do not use Store search as a substitute for immediate data retrieval. Usage:
Important limitations: This tool does not return full Actor documentation or detailed usage instructions - only summary information.
Each result lists the Actor's input fields with their types (e.g. Returns list of Actor cards with the following info:
|
| fetch-actor-detailsA | Get detailed information about an Actor by its ID or full name (format: "username/name", e.g., "apify/rag-web-browser"). Requires the exact ID or full name — do not construct a plausible-looking name and call this tool with it. If you only have a description, a partial name, or a name you have not seen in this conversation, find it with search-actors first. Use 'output' parameter with boolean flags to control returned information:
The 'readme' field returns the summary when available, full README otherwise. Use when querying Actor details, documentation, input requirements, or MCP tools. EXAMPLES:
|
| call-actorA | Call any Actor from the Apify Store. WORKFLOW:
If the actor name is not in "username/name" format, use search-actors to resolve the correct Actor first. For MCP server Actors:
IMPORTANT:
There are two ways to run Actors:
USAGE:
EXAMPLES:
|
| get-actor-runA | Get detailed information about a specific Actor run. Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep.
USAGE:
USAGE EXAMPLES:
|
| get-dataset-itemsA | Get items (rows) from a dataset — the output/results produced by an Actor run. Returns the rows themselves, not dataset metadata, counts, or a schema. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly. Default limit is 20. Use clean=true to skip empty items and hidden fields. USAGE:
USAGE EXAMPLES:
|
| get-key-value-store-recordA | Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically. USAGE:
USAGE EXAMPLES:
|
| abort-actor-runA | Abort an Actor run that is currently starting or running. For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request. USAGE:
USAGE EXAMPLES:
|
| search-apify-docsA | Search Apify and Crawlee documentation using full-text search. Do not also search the Apify Store unless the user asks to find Actors. You must explicitly select which documentation source to search using the docSource parameter: • docSource="apify" - Apify: Apify Platform documentation including: Platform features, SDKs (JS, Python), CLI, REST API, Academy (web scraping fundamentals), Actor development and deployment • docSource="crawlee-js" - Crawlee (JavaScript): Crawlee is a web scraping library for JavaScript. It handles blocking, crawling, proxies, and browsers for you. • docSource="crawlee-py" - Crawlee (Python): Crawlee is a web scraping library for Python. It handles blocking, crawling, proxies, and browsers for you. The results will include the URL of the documentation page (which may include an anchor), and a limited piece of content that matches the search query. Fetch the full content of the document using the fetch-apify-docs tool by providing the URL. When results contain both platform documentation ( |
| fetch-apify-docsA | Fetch the full content of an Apify or Crawlee documentation page by its URL. Use this after finding a relevant page with the search-apify-docs tool. USAGE:
USAGE EXAMPLES:
|
| report-problemA | Report a problem with Apify's MCP tools or Actors to the Apify team. Call it when:
Put what you were doing and what went wrong in "message". Do NOT include personal data, credentials, secrets, or verbatim private conversation content — describe the issue in your own words. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a clearly distinct resource or action: actor discovery, actor details, execution, run status, aborting, dataset retrieval, KV record retrieval, docs search, docs fetch, and problem reporting. The two search tools and two fetch tools are cleanly separated by domain (Actors/Store vs. documentation), so an agent should not confuse them.
All tool names follow a consistent lowercase hyphenated verb_noun pattern: abort-*, search-*, fetch-*, call-*, get-*. Verbs and objects are predictable, making the set easy to navigate.
Ten tools is well-scoped for an Apify/MCP integration. Each tool covers a necessary step in the core workflow without feeling bloated or redundant.
The tool set covers the full actor lifecycle well: discovery, detail lookup, invocation, run monitoring, aborting, and result retrieval. Minor gaps exist, such as listing previous runs or managing key-value stores more broadly, but agents can complete standard workflows end-to-end.