Apparatus / Setup & reference

Connect your MCP client

Complete the prerequisites first

Follow Pilot setup. Install an official extension and pair it first; the commands below do not bypass access controls or replace browser pairing.

Pilot uses remote HTTP MCP with Identity authorization. Use the same GhostStack account in your client and browser extension.

Claude Code

Run:

claude mcp add --transport http pilot https://apparatus.ghoststack.app/mcp/pilot

Open Claude Code, run /mcp, select Pilot and follow the authentication prompt. Complete Identity login and consent in your browser. Then use /mcp to inspect the connection.

Adding a server writes configuration; it does not itself prove authentication or browser pairing. Ask the agent to list connected browsers as described in the first connection check.

The command and authentication pattern follow the official Claude Code MCP documentation. Client UI and version-specific behavior may change.

Cursor

Merge this entry into .cursor/mcp.json for a project, or ~/.cursor/mcp.json for your user configuration. Preserve any existing servers.

{
  "mcpServers": {
    "pilot": {
      "url": "https://apparatus.ghoststack.app/mcp/pilot"
    }
  }
}

Open Cursor’s MCP tools settings, enable Pilot and complete its authorization prompt. Review the tools before enabling them for the agent. Verify that your paired browser is listed before requesting a page action.

Configuration locations and remote server syntax follow the official Cursor MCP documentation. This configuration is based on the documented client contract; a full production connection for each client is a release check.

Other MCP clients

Use a client that supports remote HTTP MCP and OAuth. Enter the Pilot endpoint as the server URL, then authorize with Identity. A client that only supports local stdio processes cannot use this URL as an executable command.

Never paste session cookies or account passwords into a chat prompt or commit them into client configuration.

Confirm the browser connection

A client can authenticate while the extension is disconnected. If tools are visible but no browser is available, return to the Pilot popup and check pairing, session permissions and the selected browser. See troubleshooting.