Skip to main content
GhostStackTools beyond the prompt
Menu

Explore GhostStack

Navigation

Pilot access. Official extensions available. Full production onboarding under verification.

Apparatus / Setup & reference

Set up Pilot

Check access before you start

Pilot connects an MCP client to your own Chrome browser. Check its current access notice above and the service availability reference before connecting. A store download and service authorization are separate steps.

You need a GhostStack account, an official Pilot extension, and a client that supports remote HTTP MCP with OAuth. Each service has its own access requirements.

Create your account

  1. Open Create account and continue to Identity.
  2. Complete the registration and email verification steps shown there.
  3. Sign in and open Apparatus from your account.
  4. Use this same account when pairing the extension and authorizing your MCP client.

Your personal workspace is created through Identity. You do not need a Prospector or Vault subscription to follow the Pilot path.

Install and pair the extension

Choose one official Chrome Web Store extension. For variant-specific behavior, first tasks and troubleshooting, open the Pilot usage guide or Pilot Stealth usage guide.

  • GhostStack Pilot: the standard variant.
  • GhostStack Pilot Stealth: the strict trusted-input variant, with no synthetic-click fallback. Both variants use trusted clicks and request browser permissions. Stealth also uses paced form input; it does not guarantee invisibility to websites.
  1. Open the chosen listing and select Add to Chrome.
  2. Review Chrome’s permissions and confirm installation.
  3. Open the extension toolbar popup and choose Pair browser.
  4. Sign in through Identity with the same account you will use for your MCP client.
  5. Review the authorization request and return to the popup to confirm connection.

You do not need Developer mode for a store installation. Approved developers testing a reviewed ZIP can use chrome://extensions, enable Developer mode and choose Load unpacked for the folder containing manifest.json.

Connect your client

Add this as a remote HTTP MCP server, not a local command:

https://apparatus.ghoststack.app/mcp/pilot

Follow the client setup guide for Claude Code or Cursor. Complete the client’s Identity authorization flow. The extension connection and the MCP client connection are separate steps.

Verify your first connection

  1. Keep the paired browser open and enable the session grant in Pilot.
  2. Add a domain you control or are permitted to test to the extension allowlist at read level.
  3. Ask your agent to list connected browsers using Pilot’s browsers tool.
  4. If two browsers are connected, select one explicitly or set a default.
  5. Ask it to navigate to the allowed test page and read its title in the agent’s own window.
  6. Confirm the result and activity record before granting broader access.

A configured endpoint alone does not prove the connection works. Success means the correct browser is listed and a permitted page read completes.