SimScale Edge MCP
Related Servers
Alternatives to SimScale Edge MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI-powered browser automation, web scraping, and testing using Playwright across Chromium, Firefox, and WebKit. It allows users to perform actions like navigation, clicking, typing, and taking screenshots through natural language interfaces.8 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that automates Playwright-based UI and API testing, supporting test case generation from requirements or API specs, and execution with detailed reports.6 npm1MIT
- AlicenseBqualityNot gradedmaintenanceA MCP server that provides browser automation tools, allowing users to navigate websites, take screenshots, click elements, fill forms, and execute JavaScript through Playwright.82Apache 2.0
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables browser-based QA testing of web applications using Playwright, with support for manual and AI-driven test execution and HTML reporting.-
- AlicenseBqualityDmaintenanceA browser automation server providing Playwright capabilities for controlling web browsers, capturing screenshots, extracting content, and performing complex interactions through an MCP interface.6Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides structured control of a Playwright browser for QA, scraping, diagnostics, and reproducible browser workflows.6,282 npmMIT
TDQS
Scored across 13 tools
Each tool targets a distinct browser automation concern: lifecycle (start/status/close), page reading (page_state, screenshot), navigation, and user interactions (press, click, fill, select, upload, download). The descriptions clearly separate state inspection from content inspection and from mutating actions.
All tools share the simscale_ prefix and mostly use verb-first naming (start, navigate, click, fill, select, upload, download). Minor deviation: three tools include 'edge' in the middle (simscale_edge_start/status/close) while the rest do not, and page_state is noun-based, but the pattern remains predictable.
Thirteen tools is a well-scoped set for a browser automation server. Each tool covers a necessary step in interacting with a web application, without redundancy or bloat.
The tool surface covers the full cycle: start, authenticate/check, navigate, inspect, interact, upload, wait, download, and close. Minor gaps like scrolling or hovering are absent but not critical for typical SimScale workflows, and the wait_for_text covers status transitions.