Skip to main content
← All services

Apparatus / Your browser

In testing

Pilot.
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.

PILOT / BROWSER WORKFLOWS
Choose a Pilot example
YOU ASK

Pull the important dates out of this page.

example.workspace / project
WORKSPACE
AUTUMN / PROJECT NOTES

The details. Without the digging.

01 Design review · 14 October
02 Content ready · 21 October
03 Launch check · 28 October
YOUR NEXT STEP

Three milestones, ready for your next step.

YOU ASK

Compare these two plans side by side.

example.workspace / project
WORKSPACE
AUTUMN / PROJECT NOTES

Two tabs. One clear comparison.

01 Starter · Individual workspace
02 Team · Shared workspace
03 Both · Export your work
YOUR NEXT STEP

The differences, brought into one view.

YOU ASK

Prepare the form with these project details.

example.workspace / project
WORKSPACE
AUTUMN / PROJECT NOTES

Less typing. More deciding.

01 Project · Autumn launch
02 Owner · Design team
03 Status · Ready for your review
YOUR NEXT STEP

Draft prepared. Review it before sending.

Illustrative walkthroughNo live browser connection

Connection guide

Set up Pilot.

Official extensions available. Full production onboarding under verification.

  1. Create your account

    Register through Identity, then open Apparatus from your account.

    Create account →
  2. 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.

  3. Add the MCP server

    Use a remote HTTP connection in your MCP client and authorize it through Identity.

    https://apparatus.ghoststack.app/mcp/pilot Claude Code and Cursor instructions →
  4. 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.

hello@ghoststack.app