Limetest 是最轻量级的端到端测试框架，具备 AI 功能，可在您的 CI 工作流程中运行。您可以使用自然语言定义测试用例，并让 AI 负责执行。
针对 AI 进行优化：用通俗易懂的语言定义您的测试用例，并让 AI 端到端执行它们。
轻量且高效：利用 Playwright 快照而不是像素分析来实现更快、更可靠的执行。
视觉功能：当快照模式在更复杂的测试场景中失败时，将恢复到视觉模式。
npm install @limetest/limetest
npx playwright installlimtest 将使用新的配置文件启动 Chrome 浏览器，位于
- `%USERPROFILE%\AppData\Local\ms-limetest\mcp-chrome-profile` on Windows
- `~/Library/Caches/ms-limetest/mcp-chrome-profile` on macOS
- `~/.cache/ms-limetest/mcp-chrome-profile` on LinuxRelated MCP server: Playwright MCP
使用 --headless 在 CI 工作流中无头运行测试
npx limetest examplehttps://github.com/user-attachments/assets/b801f239-dc66-4b3b-bcf2-42e2a9a68721
由Playwright提供支持的模型上下文协议 (MCP) 服务器，可简化 MCP 客户端的端到端测试。
由法学硕士 (LLM) 规划和执行的自动化测试
克隆此 repo 后，构建并将 E2E MCP 服务器添加到您的 MCP 客户端，如下所示：请注意，您需要 OpenAI API 密钥才能在端到端模式下运行此 MCP 服务器。
npm install @limetest/mcp
npx playwright install然后：
{
"mcpServers": {
"limetest": {
"command": "npx",
"args": [
"npx @limetest/mcp",
"--api-key=<your openai api key>"
]
}
}
}所有登录信息都将存储在该配置文件中，如果您想清除离线状态，可以在会话之间将其删除。
Limetest 基于微软的 Playwright MCP ，并针对作为独立框架的自动化端到端测试进行了优化。该项目遵循 Apache 2.0 许可证。
Run an end to end test suit in the browser
| Name | Required | Description | Default |
|---|---|---|---|
| testDefinition | Yes | The test case definition |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'run' which implies execution, but doesn't describe what happens during the test (e.g., browser behavior, timeouts, outputs, or side effects). This leaves significant gaps in understanding the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, straightforward sentence that efficiently conveys the core purpose. However, the typo 'suit' (likely meant 'suite') slightly detracts from clarity, preventing a perfect score.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is insufficient for a tool that executes tests. It doesn't explain what 'run' entails (e.g., whether it returns results, logs, or errors), leaving the agent without key operational context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, with the single parameter 'testDefinition' documented as 'The test case definition'. The description doesn't add any meaning beyond this, such as format examples or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Run an end to end test suit in the browser' clearly states the action (run) and target (end to end test suit in the browser). It's specific enough to understand the tool's function, though 'test suit' appears to be a typo (likely 'test suite'). Since there are no sibling tools, differentiation isn't needed, so it doesn't reach the highest score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or context for its application. It merely states what the tool does without indicating scenarios or constraints for its use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0browser_endtoendScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'browser_endtoend' follows a clear snake_case pattern.
One tool is too few for a server's purpose, as it severely limits functionality and suggests an incomplete or trivial implementation. This is a borderline case leaning toward inadequacy.
The server is severely incomplete; with only a single end-to-end test tool, there are obvious gaps in functionality for any meaningful domain, such as setup, teardown, or other testing operations.
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for Mint — AI-powered QA that runs your app in a real browser on every PR.
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
