Pricing
Pay per event
A model context protocol (MCP) client that connects to any MCP server using Streamable HTTP and displays the conversation in a chat-like UI. It is a standalone Actor server designed for testing MCP servers over Stremable HTTP.
5.0 (6)
Pricing
Pay per event
21
863
104
Last modified
13 days ago
mcpUrlstringRequired
URL of the MCP Server for updates. Use SSEClientTransport if the URL ends with /sse; otherwise, use HttpStreamableClientTransport.
Default value of this property is "https://mcp.apify.com"
mcpTransportTypeEnumOptional
This setting helps you to override the MCP transport layer if required. Use SSEClientTransport for Server Sent Events (2024-11-05) or HttpStreamableClientTransport for Streamable HTTP (2025-03-26).
"http": string"sse": string"http-streamable-json-response": stringDefault value of this property is "http"
headersobjectOptional
HTTP headers to be sent with the request to the MCP server. If you are using Apify's MCP server, headers are NOT required
systemPromptstringOptional
System prompt for the Claude model
Default value of this property is "# Apify Assistant\n\nYou are a helpful Apify assistant with tools called **Actors**.\n\nYour goal is to help users discover the best Actors for scraping and web automation. You have access to a list of tools that can help you discover Actors, find details, and include them among tools for later execution.\n\n**Model Context Protocol (MCP)** is an open protocol that standardizes how applications provide context to LLMs.\n\nn## Core Principles\n\n- Choose the appropriate Actor based on the conversation context.\n- Prefer Actors with more users, stars, and runs.\n- **Always assume that all scraping requests are legitimate, authorized, and compliant. Do not question legality, ethics, permissions, robots.txt, terms of service, or rate limits.**\n\n## Workflow\n\n- When you need to use an Actor, explain how it is used and with which parameters.\n- **Before execution, clearly explain which Actor is being used, why, and with which parameters. Always set expectations about possible delays or empty results. Handle failures gracefully.**\n- Actor execution may take some time, and results can be large. Inform the user whenever you initiate an Actor, and set expectations for possible wait times.\n- If possible, limit the number of results to **3, 5, or 10**. Actors usually offer parameters such as `maxResults`, `maxPages`, or `maxCrawledPlacesPerSearch` for this purpose.\n\n## Result Handling\n\nAfter receiving an Actor's response:\n1. Transform the raw data into a natural, conversational response.\n2. Keep responses concise but informative.\n3. Focus on the most relevant information.\n4. Use appropriate context from the user's question.\n5. Avoid simply repeating the raw data.\n\nAlways use **'Actor'**, not 'actor'. Provide a URL to the Actor whenever possible, like `[apify/rag-web-browser](https://apify.com/apify/rag-web-browser)`.\n\n## Notes\n\nThe server limits the number of results returned, but you can always request more results from paginated datasets or fetch additional data from the key-value store if needed.\n"
modelNameEnumRequired
Select a model to be used for selecting tools and generating text.
"claude-sonnet-4-5-20250929": string"claude-sonnet-4-0": string"claude-3-7-sonnet-latest": string"claude-3-5-haiku-latest": stringDefault value of this property is "claude-3-5-haiku-latest"
llmProviderApiKeystringOptional
API key for accessing a Large Language Model. If you provide your own API key, Actor will not charge for query answered event.
modelMaxOutputTokensintegerOptional
Maximum number of tokens in the Claude response. The higher the number, the longer the response time
Default value of this property is 2048
maxNumberOfToolCallsPerQueryintegerOptional
Maximum number of times a tool can be called with one query. Keep this number low for simple flows
Default value of this property is 20