[Feature]: Enable Test Engine Integration with Playwright MCP Server via Test Engine MCP Server

该 issue 没有列出文件、测试或入口点。首先定位 Test Engine 的集成接口及其现有的 Playwright 相关会话处理，然后明确 MCP 服务器、会话复用、提示执行和 VS Code 兼容性方面的要求范围；完成的标准是这四项能力能够通过兼容 stdio 的接口协同工作。

Is your feature request related to a problem? Please describe.

Enable Power Apps Test Engine to integrate with Playwright MCP Server by exposing a stdio-compatible interface. This would allow prompt-driven test automation workflows to leverage Test Engine capabilities without requiring manual scripting in TypeScript or Power Fx.

Motivation

Current limitations in Playwright’s ability to snapshot and navigate complex iframe structures in Power Apps hinder UI automation. While Test Engine provides deep access to the JavaScript object model for entitylist and entityrecord controls, it is not currently accessible via MCP workflows.

This feature would allow users to:

• Run tests using natural language prompts via GenAIScript, Semantic Kernel, or GenKit.
• Reuse authentication and session state from Playwright MCP Server.
• Automate Model Driven App testing without writing traditional test code.
• Capture screenshots and documentation directly from VS Code using MCP agent mode

Describe the solution you'd like

1. Expose MCP Server for Test Engine

   • Implement a stdio-compatible interface that allows Test Engine to act as an MCP server.
   • Register Test Engine capabilities as callable MCP tools with metadata (name, description, inputs/outputs).

2. Enable Session State Reuse

   • Support persisted session state from Playwright MCP to maintain authentication across test runs.

3. Support Prompt-Based Test Execution

   • Allow prompt-driven invocation of Test Engine features using GenAIScript or similar frameworks.

4. VS Code Compatibility

   • Ensure Test Engine tools are discoverable and usable within VS Code’s MCP agent mode.

Benefits

• Eliminates the need for manual scripting in Power Fx or TypeScript and leverage MCP action integration
• Enables low-code/no-code testers to automate scenarios using natural language.
• Bridges browser-level automation with platform-specific control access.
• Accelerates adoption of AI-driven testing workflows.

Describe alternatives you've considered

No response

Additional context?

No response