Apparatus / Your browser
In testingPilot.
Give your agent a browser you control.
Your browser for your agent. Check access and setup below.
What to expect
Your browser, connected to your workflow.
Connect an MCP client to your own Chrome browser. Read pages, navigate and interact with controls within the permissions you grant in the extension. Pilot is the first service intended for public access; both extension variants are listed in the Chrome Web Store, while the coordinated production onboarding path remains under verification.
Pull the important dates out of this page.
The details. Without the digging.
Three milestones, ready for your next step.
Compare these two plans side by side.
Two tabs. One clear comparison.
The differences, brought into one view.
Prepare the form with these project details.
Less typing. More deciding.
Draft prepared. Review it before sending.
Connection guide
Set up Pilot.
Official extensions available. Full production onboarding under verification.
-
Create your account
Register through Identity, then open Apparatus from your account.
Create account → -
Install and pair
Install Pilot or Install Pilot Stealth from the Chrome Web Store.
Install one official variant, then choose Pair browser in the extension and sign in with the same account.
-
Add the MCP server
Use a remote HTTP connection in your MCP client and authorize it through Identity.
https://apparatus.ghoststack.app/mcp/pilotClaude Code and Cursor instructions → -
Test a read-only action
Enable the session in the extension, allow a test domain at read level, then ask your agent to list connected browsers and read a page in its own window.
Before you connect
- A GhostStack account and access to Apparatus.
- Chrome with GhostStack Pilot or GhostStack Pilot Stealth from the Chrome Web Store.
- An MCP client that supports remote HTTP servers and OAuth.
Need help?
Include the service name and error code. Keep account tokens and private page content out of your message.