Serialize’s interactive workspace and page-local WebMCP recipe execution run inside the browser page. This is the preferred path for sensitive local data because the recipe input is not sent to Serialize’s public MCP endpoint.
What stays local
- Text or files placed in the workspace
- Intermediate and final recipe output
- Page-local
serialize_run_recipeexecution - Workflows saved to browser storage
Important exceptions
Some operations are network-capable by their nature. Inspect an operation before using it with confidential data, especially fetch, DNS, URL, or external lookup operations. Deep links can include both workflow and input data in the URL, so review a link before sharing it.
Standard MCP boundary
The public endpoint at https://serialize.dev/mcp accepts catalogue search and exact operation-name description requests. It does not accept recipe input and cannot execute recipes.