Greet anyone by name with friendly, personalized messages. Explore the origin of Hello, World thro…
ai.smithery/jirispilka-actors-mcp-server MCP Server
This MCP server supports greeting workflows by name with friendly, personalized messages. Its description also indicates it can explore the origin of “Hello, World”, based on the server’s provided summary. Additional details are available in the repository excerpt.
🛠️ Key Features
Personalized greetings by name
Exploration of the origin of “Hello, World”
🚀 Use Cases
Generate user-specific welcome or greeting messages
Provide context or history for the “Hello, World” example
⚡ Developer Benefits
Straightforward greeting behavior tied to input name
Content focused on “Hello, World” origin, suitable for documentation or explanations
⚠️ Limitations
The provided data does not specify tools, capabilities beyond the greeting and “Hello, World” origin, or any tool count.
The Apify Model Context Protocol (MCP) Server at mcp.apify.com instantly connects AI applications and agents to thousands of ready‑built tools. It allows your AI assistant to use any Apify Actor for web scraping, data extraction, and automation tasks in real time.
🚀 Try the hosted Apify MCP Server!
For the easiest setup and most powerful features, including the ability to find and use any Actor from Apify Store, connect your AI assistant to our hosted server:
Use Instagram Scraper to scrape Instagram posts, profiles, places, photos, and comments.
Use RAG Web Browser to search the web, scrape the top N URLs, and return their content.
Video tutorial: Integrate 5,000+ Apify Actors and Agents with Claude
🚀 Quickstart
You can use the Apify MCP Server in two ways:
HTTPS Endpoint (mcp.apify.com): Connect from your MCP client via OAuth or by including the Authorization: Bearer <APIFY_TOKEN> header in your requests. This is the recommended method for most use cases. Because it supports OAuth, you can connect from clients like Claude.ai or Visual Studio Code using just the URL: https://mcp.apify.com.
https://mcp.apify.com (recommended) for streamable transport
https://mcp.apify.com/sse for legacy SSE transport
Standard Input/Output (stdio): Ideal for local integrations and command-line tools like the Claude for Desktop client.
Set the MCP client server command to npx @apify/actors-mcp-server and the APIFY_TOKEN environment variable to your Apify API token.
See npx @apify/actors-mcp-server --help for more options.
You can find detailed instructions for setting up the MCP server in the Apify documentation.
🤖 MCP clients and examples
To interact with the Apify MCP server, you can use various MCP clients, such as:
This interactive, chat-like interface provides an easy way to explore the capabilities of Apify MCP without any local setup.
Just sign in with your Apify account and start experimenting with web scraping, data extraction, and automation tools!
Or use the Anthropic Desktop extension file (dxt) for one-click installation: Apify MCP server dxt file
🛠️ Tools, resources, and prompts
The MCP server provides a set of tools for interacting with Apify Actors.
Since the Apify Store is large and growing rapidly, the MCP server provides a way to dynamically discover and use new Actors.
Actors
Any Apify Actor can be used as a tool.
By default, the server is pre-configured with one Actor, apify/rag-web-browser, and several helper tools.
The MCP server loads an Actor's input schema and creates a corresponding MCP tool.
This allows the AI agent to know exactly what arguments to pass to the Actor and what to expect in return.
For example, for the apify/rag-web-browser Actor, the input parameters are:
json
{"query":"restaurants in San Francisco","maxResults":3}
You don't need to manually specify which Actor to call or its input parameters; the LLM handles this automatically.
When a tool is called, the arguments are automatically passed to the Actor by the LLM.
You can refer to the specific Actor's documentation for a list of available arguments.
Helper tools
One of the most powerful features of using MCP with Apify is dynamic tool discovery.
It gives an AI agent the ability to find new tools (Actors) as needed and incorporate them.
Here are some special MCP operations and how the Apify MCP Server supports them:
Actor discovery and management: Search for Actors, view their details, and dynamically add or remove them as available tools for the AI.
Apify documentation: Search the Apify documentation and fetch specific documents to provide context to the AI.
Actor runs (*): Get lists of your Actor runs, inspect their details, and retrieve logs.
Apify storage (*): Access data from your datasets and key-value stores.
Note: Helper tool categories marked with (*) are not enabled by default in the MCP server and must be explicitly enabled using the tools argument (either the --tools command line argument for the stdio server or the ?tools URL query parameter for the remote MCP server). The tools argument is a comma-separated list of categories with the following possible values:
docs: Search and fetch Apify documentation tools.
runs: Get Actor run lists, run details, and logs from a specific Actor run.
storage: Access datasets, key-value stores, and their records.
preview: Experimental tools in preview mode.
For example, to enable all tools, use npx @apify/actors-mcp-server --tools docs,runs,storage,preview or https://mcp.apify.com/?tools=docs,runs,storage,preview.
Overview of available tools
Here is an overview list of all the tools provided by the Apify MCP Server.
Tool name
Category
Description
Enabled by default
get-actor-details
default
Retrieve detailed information about a specific Actor.
Search the Apify documentation for relevant pages.
✅
fetch-apify-docs
docs
Fetch the full content of an Apify documentation page by its URL.
✅
call-actor
preview
Call an Actor and get its run results.
get-actor-run
runs
Get detailed information about a specific Actor run.
get-actor-run-list
runs
Get a list of an Actor's runs, filterable by status.
get-actor-log
runs
Retrieve the logs for a specific Actor run.
get-dataset
storage
Get metadata about a specific dataset.
get-dataset-items
storage
Retrieve items from a dataset with support for filtering and pagination.
get-key-value-store
storage
Get metadata about a specific key-value store.
get-key-value-store-keys
storage
List the keys within a specific key-value store.
get-key-value-store-record
storage
Get the value associated with a specific key in a key-value store.
get-dataset-list
storage
List all available datasets for the user.
get-key-value-store-list
storage
List all available key-value stores for the user.
Prompts
The server provides a set of predefined example prompts to help you get started interacting with Apify through MCP. For example, there is a GetLatestNewsOnTopic prompt that allows you to easily retrieve the latest news on a specific topic using the RAG Web Browser Actor.
Upon launching, the Inspector will display a URL that you can open in your browser to begin debugging.
🐦 Canary PR releases
Due to the current architecture where Apify MCP is split across two repositories, this one containing the core MCP logic and the private apify-mcp-server repository that handles the actual server implementation for mcp.apify.com, development can be challenging as changes need to be synchronized between both repositories.
You can create a canary release from your PR branch by adding the beta tag. This will test the code and publish the package to pkg.pr.new which you can then use, for example, in a staging environment to test before actually merging the changes. This way we do not need to create new NPM releases and keep the NPM versions cleaner. The workflow runs whenever you commit to a PR branch that has the beta tag or when you add the beta tag to an already existing PR. For more details check out the workflow file.
🐛 Troubleshooting (local MCP server)
Make sure you have node installed by running node -v.
Make sure the APIFY_TOKEN environment variable is set.
Always use the latest version of the MCP server by using @apify/actors-mcp-server@latest.
💡 Limitations
The Actor input schema is processed to be compatible with most MCP clients while adhering to JSON Schema standards. The processing includes:
Descriptions are truncated to 500 characters (as defined in MAX_DESCRIPTION_LENGTH).
Enum fields are truncated to a maximum combined length of 200 characters for all elements (as defined in ACTOR_ENUM_MAX_LENGTH).
Required fields are explicitly marked with a REQUIRED prefix in their descriptions for compatibility with frameworks that may not handle the JSON schema properly.
Nested properties are built for special cases like proxy configuration and request list sources to ensure the correct input structure.
Array item types are inferred when not explicitly defined in the schema, using a priority order: explicit type in items > prefill type > default value type > editor type.
Enum values and examples are added to property descriptions to ensure visibility, even if the client doesn't fully support the JSON schema.
Rental Actors are only available for use with the hosted MCP server at https://mcp.apify.com. When running the server locally via stdio, you can only access Actors that are already added to your local toolset. To dynamically search for and use any Actor from the Apify Store—including rental Actors—connect to the hosted endpoint.
🤝 Contributing
We welcome contributions to improve the Apify MCP Server! Here's how you can help:
🐛 Report issues: Find a bug or have a feature request? Open an issue.
🔧 Submit pull requests: Fork the repo and submit pull requests with enhancements or fixes.
📚 Documentation: Improvements to docs and examples are always welcome.
💡 Share use cases: Contribute examples to help other users.
For major changes, please open an issue first to discuss your proposal and ensure it aligns with the project's goals.
