1. Set up the connection and authorize only the test profile
Prepare a test profile
Start the local test page as described in the profile isolation tutorial and save the A marker in profile A. Keep the fictitious test data for now so you can check the output.
Open Prism’s access panel
Go to “Local AI · MCP” and turn on the AI control switch for the test profile. If MCP is not enabled yet, enable it, then use “Copy MCP Configuration”; a service that is already running does not need to be stopped and restarted.
Check WorkBuddy’s connector settings
In this test, the path was “Experts · Skills · Connectors → Connectors → Custom Connectors → MCP Service Management → Configure MCP” (translated from the Chinese interface). Merge the prism entry into the existing configuration and keep the other server entries.
Confirm the tools are available
Make sure the prism connector is enabled and reconnect as the client prompts. This test used the existing, already enabled configuration; if you see a path or connection error, first compare the configuration Prism generated with the installation location on your computer.
Configuration shape for the Mac installation used here
Prefer copying the configuration provided by your current Prism app; do not use a macOS path on Windows.
{
"mcpServers": {
"prism": {
"command": "/Applications/Prism Browser.app/Contents/Resources/pro-agent/prism-pro-agent",
"args": [
"--mcp"
]
}
}
}2. State the goal and scope in a new task
Replace the profile name below with the name of your actual test profile. Keep the local test server running; if you used a different port, change the address in the task too.
Use only the temporary profile I specified, “Tutorial Test-A”. Create a separate task session through Prism MCP, open http://127.0.0.1:4318/, and read the page title, the test ID and the Cookie and localStorage markers shown on the page. Do not click, fill in or submit anything, do not modify local files, skills or settings, and do not read any other profile. When finished, release the task session you created and keep the profile. If MCP is unavailable, report the error instead of using another method.
Ask the client to report the actual tool calls and returned results. A bare “Done” does not prove the connection worked; check the output against what you know is on the page.
3. What was read in this test
| Check | Observed | Conclusion |
|---|---|---|
| Page title | Prism profile isolation test | Match |
| Test ID | PRISM-SEO-20260924 | Match |
| Cookie / localStorage | A / A | Match |
| Task session | Created and released; the profile could then be closed | Connection and reading passed |
| No changes to local files | Modified a skill note after reading | Failed |
These records come from WorkBuddy’s results screen and observations during the test. On the Prism side, a separate page snapshot confirmed A/A, and the profile closed successfully after the session ended. The client’s own summary should not be taken as independent verification of every step.
4. What task instructions and tool permissions each control
In this test, WorkBuddy did not click any buttons on the test page and completed the required reading, but then modified a local skill note on its own, going beyond the “do not modify files” instruction. The tester stopped the task and removed the newly added note.
So this result supports “WorkBuddy can read authorized profiles through Prism MCP”, but not “the AI client as a whole always stays strictly read-only”. Prism’s profile switches control which browser profiles can be accessed; they do not restrict WorkBuddy’s file, terminal or other tools for you. Before real tasks, also check the AI client’s own tool permissions and execution logs.
Local stdio is only the connection method. Page content read by AI enters the WorkBuddy workflow, and whether it is sent to a remote model depends on the client and the model service; see Data and privacy for details.
5. Release the session, then revoke profile access
Have the task release its own session
Use prism_close_task_session to end the page controller that the task created. Releasing the session does not close the browser profile; close the profile separately if needed.
Turn off AI access for the profile
Go back to “Local AI · MCP” in Prism and turn off access for the test profile. After access was revoked in this test, requests to the profile returned “This profile does not yet allow local AI control”.
Check the wrap-up
Confirm that access to the test profile is revoked, your session is released and other tasks are unaffected. When you are done testing, stop the local test page server.
If connecting or closing fails
- The prism tools are missing
- Check that the connector is enabled, that the app’s installation path matches the generated configuration, and the status of Prism’s MCP service. Do not take the model’s claim that it “can do it” as proof of a connection.
- The profile is reported as not authorized
- Check the name and number of the profile the access switch belongs to, and grant access only to the target profile for this task. If you just revoked access yourself, this refusal is exactly what should happen.
- PROFILE_IN_USE error
- Check for active task sessions; have the owning task release its session first, then close the profile.
- Single A/B letters are not read
- The default compact snapshot may filter out single-character text. Check with a full snapshot (
compact:false) or a visible-page-text tool instead.
Next: expand the task as needed
First confirm the target profile and the returned results, then define which clicks or form entries are allowed for your actual use. The MCP feature page explains how to stop control and more; the edition comparison explains how Pro differs from free profile management.
Sources and corrections
For this article, Codex operated the installed Prism app, called Prism MCP and compiled the actual results; the screenshots were taken during that process. This is a product walkthrough published by the official Prism website, not an independent third-party review, and no untested platform or version is described as passing.
For the product maintainer and contact details, see About Prism. If your results differ, report your OS, Prism and kernel versions, exact steps and redacted screenshots in GitHub Issues; do not attach cookies, activation codes or proxy passwords.