
Tester MCP Client
Pricing
Pay per event

Tester MCP Client
A model context protocol (MCP) client that connects to any MCP server using Server-Sent Events (SSE) and displays the conversation in a chat-like UI. It is a standalone Actor server designed for testing MCP servers over SSE.
4.8 (5)
Pricing
Pay per event
11
Total users
292
Monthly users
208
Runs succeeded
0%
Last modified
2 days ago
You can access the Tester MCP Client programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.
$# Start Server-Sent Events (SSE) session and keep it running<curl "https://actors-mcp-server.apify.actor/sse?token=<YOUR_API_TOKEN>&actors=jiri.spilka/tester-mcp-client"
# Session id example output:# event: endpoint# data: /message?sessionId=9d820491-38d4-4c7d-bb6a-3b7dc542f1fa
Using Tester MCP Client via Model Context Protocol (MCP) server
MCP server lets you use Tester MCP Client within your AI workflows. Send API requests to trigger actions and receive real-time results. Take the received sessionId
and use it to communicate with the MCP server. The message starts the Tester MCP Client Actor with the provided input.
$curl -X POST "https://actors-mcp-server.apify.actor/message?token=<YOUR_API_TOKEN>&session_id=<SESSION_ID>" -H "Content-Type: application/json" -d '{$ "jsonrpc": "2.0",$ "id": 1,$ "method": "tools/call",$ "params": {$ "arguments": {$ "mcpUrl": "https://actors-mcp-server.apify.actor/sse?enableAddingActors=true",$ "systemPrompt": "You 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.\\nYou have access to a list of tools that can help you discover Actors, find details, and include them among tools for later execution.\\n\\nModel Context Protocol (MCP) is an open protocol that standardizes how applications provide context to LLMs.\\n\\nChoose the appropriate Actor based on the conversation context. If no Actor is needed, reply directly.\\n\\nPrefer Actors with more users, stars, and runs.\\nWhen you need to use an Actor, explain how it is used and with which parameters.\\nNever call an Actor unless it is required by the user!\\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.\\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)`.\\nREMEMBER: Always limit the number of results returned from Actors.\\nThere is always a parameter such as `maxResults=1`, `maxPage=1`, `maxCrawledPlacesPerSearch=1`. Keep it to the minimal value.\\nOtherwise, Actor execution takes a long time and the result can be huge!\\nAlways inform the user that calling an Actor might take some time.\\n",$ "modelMaxOutputTokens": 2048,$ "maxNumberOfToolCallsPerQuery": 10,$ "toolCallTimeoutSec": 300$},$ "name": "jiri.spilka/tester-mcp-client"$ }$}'
The response should be: Accepted
. You should received response via SSE (JSON) as:
$event: message$data: {$ "result": {$ "content": [$ {$ "type": "text",$ "text": "ACTOR_RESPONSE"$ }$ ]$ }$}
Configure local MCP Server via standard input/output for Tester MCP Client
You can connect to the MCP Server using clients like ClaudeDesktop and LibreChat or build your own. The server can run both locally and remotely, giving you full flexibility. Set up the server in the client configuration as follows:
{ "mcpServers": { "actors-mcp-server": { "command": "npx", "args": [ "-y", "@apify/actors-mcp-server", "--actors", "jiri.spilka/tester-mcp-client" ], "env": { "APIFY_TOKEN": "<YOUR_API_TOKEN>" } } }}
You can further access the MCP client through the Tester MCP Client, a chat user interface to interact with the server.
To get started, check out the documentation and example clients. If you are interested in learning more about our MCP server, check out our blog post.