TestCafe MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_testC | Create a TestCafe test file from structured test definition |
| execute_testC | Execute TestCafe tests with configurable browsers and options |
| validate_testC | Validate TestCafe test syntax, structure, and best practices |
| interactC | Perform browser interactions and generate TestCafe test code |
| inspect_pageC | Inspect web pages, discover elements, and generate selectors for TestCafe automation |
| get_console_logsC | Capture and retrieve browser console logs (errors, warnings, info, debug) from a web page. Essential for debugging JavaScript issues. |
| get_accessibility_snapshotC | Return the accessibility tree of a web page - structured, LLM-friendly data about page content including roles, labels, and states without requiring vision. Essential for understanding page structure and interactive elements. |
| browser_tabsB | Manage browser tabs/windows - list all open tabs, create new tabs, close tabs, and switch between tabs. Note: TestCafe manages windows rather than traditional tabs, but the functionality is similar. |
| get_network_logsB | Capture network requests and responses for debugging and API verification. Supports filtering by URL pattern, HTTP method, status code, and resource type. Essential for understanding API calls and debugging network issues. |
| handle_dialogsB | Capture and handle native browser dialogs (alert, confirm, prompt, beforeunload). Auto-dismiss with defaults or use custom response logic for testing. |
| browser_navigateC | Navigate to a URL in the persistent browser session |
| browser_snapshotB | Capture accessibility snapshot of the current page, this is better than screenshot |
| browser_clickD | Perform click on a web page |
| browser_typeC | Type text into editable element |
| browser_press_keyC | Press a key on the keyboard |
| browser_evaluateC | Evaluate JavaScript expression on page or element |
| browser_take_screenshotA | Take a screenshot of the current page. You can't perform actions based on the screenshot, use browser_snapshot for actions. |
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 17 tools
All tools have clearly distinct purposes. Browser interaction tools are prefixed with 'browser_' and each targets a specific action (navigate, click, type, etc.). Logging and snapshot tools are also well-separated (console, network, accessibility). No overlap in functionality.
Most tools follow a consistent verb_noun pattern using snake_case (e.g., create_test, browser_navigate). A few tools like 'interact' and 'inspect_page' deviate slightly but are still clear. Overall, the naming is predictable and easy to navigate.
With 17 tools, the server strikes a good balance. Each tool serves a distinct purpose for TestCafe automation—test creation, execution, validation, browser interactions, logging, and debugging—without being overwhelming.
The tool set covers the core TestCafe workflow: creating tests, running them, interacting with pages, capturing logs and snapshots, and handling dialogs. Minor gaps exist (e.g., no tool for listing/deleting tests, no explicit scroll or hover), but the overall surface is comprehensive for typical automation tasks.