SimScale Edge MCP
The SimScale Edge MCP server enables programmatic automation of the SimScale Workbench through Microsoft Edge, without using the enterprise API. You can:
Browser Management: Start, check status, and close a persistent Edge session connected to SimScale.
Observation: Navigate to HTTPS SimScale pages, read the UI state (headings, controls), capture screenshots, and wait for specific text (e.g., meshing or run status).
UI Interaction: Click, fill text fields (passwords blocked), press keys, and select dropdown options using semantic targets (label, role, test ID) for resilience to UI changes.
File Operations: Upload CAD files from a configured root directory and download results to a local folder, both requiring explicit confirmations for safety.
Project Pinning: Pin a specific project to ensure all actions remain on the intended workspace.
Safety: All mutating or compute actions require explicit confirmation flags; navigation is restricted to SimScale domains; passwords and credentials are never exposed; and the user's personal Edge browser is never closed.
Customization: Configure via environment variables (e.g., file roots, Edge profiles, timeouts).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SimScale Edge MCP Run a simulation on the wind turbine project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SimScale Edge MCP
An MCP server that navigates the SimScale Workbench through Microsoft Edge and Playwright. It does not use the enterprise SimScale API.
The recommended mode attaches to your normal, already signed-in Edge profile.
Remote debugging must be enabled from Edge's built-in edge://inspect page.
The fallback mode opens a separate MCP-managed profile.
Requirements
Node.js 20 or newer
Microsoft Edge
A SimScale account
Related MCP server: Playwright Server MCP
Install
npm installPlaywright Core drives the copy of Microsoft Edge already installed on Windows; it does not download a separate browser.
Start the host broker
Codex's command sandbox can prevent a stdio MCP child from completing Edge's DevTools WebSocket upgrade. Start the loopback-only host broker from a normal PowerShell window before opening Codex:
powershell -ExecutionPolicy Bypass -File .\scripts\start-simscale-host.ps1The broker listens only on 127.0.0.1:43127. Stop it when finished with:
powershell -ExecutionPolicy Bypass -File .\scripts\stop-simscale-host.ps1Connect an MCP host
Use the broker's Streamable HTTP endpoint:
{
"mcpServers": {
"simscale": {
"url": "http://127.0.0.1:43127/mcp"
}
}
}The launcher sets SIMSCALE_FILE_ROOT to this project directory. It restricts
which local files the MCP may upload and is also where result downloads are
saved. Change that assignment in scripts/start-simscale-host.ps1 if your CAD
files live elsewhere.
Optional environment variables:
Variable | Default | Purpose |
| MCP working directory | Allowed upload/download root |
| unset | Discover a debugging-enabled Edge instance |
| unset | Advanced fixed-port attachment override |
|
| Edge attachment timeout, from 5 to 120 seconds |
|
| Persistent Edge profile |
|
| Playwright browser channel |
| SimScale My Projects | Initial page |
| unset | Set to enable advanced CSS targets |
Use your already signed-in Edge profile
Run the helper to open Edge's supported remote-debugging settings:
powershell -ExecutionPolicy Bypass -File .\scripts\start-edge-debug.ps1On the Remote debugging page, enable Allow remote debugging for this
browser instance. Set SIMSCALE_EDGE_USER_DATA_DIR to Edge's user-data
directory (normally %LOCALAPPDATA%\Microsoft\Edge\User Data). The MCP reads
only Edge's DevToolsActivePort handshake file, attaches to that Edge instance,
and opens or reuses a SimScale tab. It does not read cookies or profile files and
will not close your personal Edge browser.
If an MCP process is forcibly stopped while attached, toggle remote debugging off and on before reconnecting. Restart the MCP host after changing its server registration or updating this server's code so it launches a fresh process.
Remote debugging gives local software control over browser tabs. Edge binds its debugging endpoint locally, and this MCP restricts its navigation to HTTPS SimScale domains. Turn remote debugging off when finished.
First MCP use
Call
simscale_edge_start.Call
simscale_edge_statusand verifyconnectionModeisattachedandsignedInistrue.Call
simscale_select_pagewith the expected SimScaleproject_id. The MCP pins that project and prefers its Workbench tab over Dashboard tabs.Call
simscale_wait_for_workbench_ready, thensimscale_page_statebefore each interaction. Usecontainer,text_filter,offset, andmax_itemsto retrieve the relevant slice of a large Workbench tree.Prefer the returned
element_id, followed bytest_id, role/name, or label withsimscale_click,simscale_fill,simscale_select, andsimscale_press.Pass the pinned project as
expected_project_idon every navigation or UI-changing tool. The MCP rejects missing or mismatched project IDs before interacting.
Action tools optionally accept expect_text, expect_url, expect_value, and
expect_timeout_ms. Their results include the current project, simulation, and
run identity so callers can verify that the intended Workbench state remained
active.
For CAD uploads, point SIMSCALE_FILE_ROOT at the CAD folder and use
simscale_upload_file with confirm_upload: true. Starting a mesh or simulation
run, saving, creating, deleting, or other state-changing clicks require
confirm_action: true.
Available tools
simscale_edge_start,simscale_edge_status,simscale_edge_closesimscale_edge_diagnosticssimscale_select_page,simscale_wait_for_workbench_readysimscale_page_state,simscale_screenshot,simscale_navigatesimscale_click,simscale_fill,simscale_press,simscale_selectsimscale_upload_file,simscale_downloadsimscale_wait_for_text
The tools are deliberately semantic instead of hard-coding SimScale's current DOM structure. The agent reads the live interface and targets visible, accessible labels, which makes the MCP more resilient to Workbench updates.
Test
npm testTests do not launch Edge or access SimScale.
Safety
Password fields cannot be filled or read through MCP.
Cookies, browser storage, and saved credentials are never exposed.
CDP attachment is restricted to explicit HTTP or WebSocket loopback ports.
Navigation is restricted to HTTPS SimScale domains.
Project pages can be pinned, and UI-changing tools require a matching
expected_project_id.Uploads are restricted to
SIMSCALE_FILE_ROOTand require confirmation.Downloads require confirmation and go to
simscale-downloads.Mutating, destructive, and compute-related clicks require confirmation.
Attached mode never closes the user's personal Edge browser.
Available Tools
13 toolssimscale_clickA
Click one unique visible SimScale control using its role, label, text, or test ID. Mutating or compute-related labels require confirm_action=true.
Inputs: target (required), confirm_action.
simscale_downloadA
Click a unique SimScale download control and save the result under SIMSCALE_FILE_ROOT/simscale-downloads. Requires confirm_download=true.
Inputs: target (required), confirm_download (required).
simscale_edge_closeAIdempotent
Close the MCP-managed Edge window. The persistent login profile remains for the next session.
Inputs: no named parameters.
simscale_edge_startA
Open SimScale in a persistent Microsoft Edge profile. Log in manually if needed.
Inputs: no named parameters.
simscale_edge_statusARead-onlyIdempotent
Check whether Edge is running and whether the current SimScale page appears signed in.
Inputs: no named parameters.
simscale_fillA
Fill one unique visible SimScale field. Password fields are blocked and must be completed manually in Edge.
Inputs: value (required), target (required).
simscale_page_stateARead-onlyIdempotent
Read the current SimScale page's headings, notices, and visible interactive controls without exposing passwords or cookies.
Inputs: max_items.
simscale_pressA
Press a keyboard key on one unique visible SimScale control, such as Enter or Escape.
Inputs: key (required), target (required).
simscale_screenshotARead-only
Capture the current visible SimScale viewport as a PNG image.
Inputs: no named parameters.
simscale_selectC
Choose an option in a native SimScale select control.
Inputs: option (required), target (required).
simscale_upload_fileA
Upload a CAD or other local file from SIMSCALE_FILE_ROOT through a visible file input. Requires confirm_upload=true.
Inputs: target (required), file_path (required), confirm_upload (required).
simscale_wait_for_textARead-only
Wait for visible SimScale text, useful for CAD imports, meshing, and run status transitions.
Inputs: text (required), timeout_ms.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
MCP server for Mint — AI-powered QA that runs your app in a real browser on every PR.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Official Browserless MCP server: browser automation, scraping, screenshots and PDFs for AI agents.
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
Related MCP Servers
- 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
- 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 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.MIT
- 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.1MIT