Skip to main content
Using Kernel CLI (recommended):
The command will display the YAML configuration to add to your Goose config file. Each client needs a separate OAuth callback port as well as a separate cache to authorize while other clients are running. The config below uses 46096 for Goose. If you customize it, choose an unused port that no other client uses. Install link: Click here to add Kernel to Goose. When prompted, set MCP_REMOTE_CONFIG_DIR to an absolute directory dedicated to Goose so another client’s cached registration can’t be reused.

​
Goose Desktop

  1. Click Extensions in the sidebar of the Goose Desktop.
  2. Click Add custom extension.
  3. On the Add custom extension modal, enter:
    • Extension Name: Kernel
    • Type: STDIO
    • Description: Access Kernel's cloud-based browsers via MCP
    • Command: npx -y mcp-remote https://mcp.onkernel.com/mcp 46096 --static-oauth-client-metadata '{"client_name":"Goose"}'
    • Environment variable: Set MCP_REMOTE_CONFIG_DIR to an absolute directory dedicated to Goose.
    • Timeout: 300
  4. Click Save Changes button.

​
Goose CLI

  1. Run the following command:
  2. Select Add Extension from the menu.
  3. Choose Command-line Extension.
  4. Follow the prompts:
    • Extension name: Kernel
    • Command: npx -y mcp-remote https://mcp.onkernel.com/mcp 46096 --static-oauth-client-metadata '{"client_name":"Goose"}'
    • Environment variable: Set MCP_REMOTE_CONFIG_DIR to an absolute directory dedicated to Goose.
    • Timeout: 300
    • Description: Access Kernel's cloud-based browsers via MCP
If you previously authorized Kernel and the consent screen still shows MCP CLI Proxy, close Goose, update the config above, then remove the cache it used (~/.mcp-auth/mcp-remote-v1/ by default, or mcp-remote-v1/ under your custom MCP_REMOTE_CONFIG_DIR). Reopen Goose and authorize again. This also signs out other clients using that cache. The latest Kernel CLI prints a config with a separate Goose cache.