AliasMode
Download free

ChatGPT connector

Use your AliasMode profiles from ChatGPT.

ChatGPT speaks to AliasMode over Remote MCP. Add your pinned device URL once, approve it with OAuth or a bearer connector, and ChatGPT can operate persistent browser profiles on your Windows host.

Read the connector guideDownload AliasMode for Windows

Remote MCP (OAuth) — Remote MCP (bearer token) — Windows — Tested 2026-09-01

Direct answer

Enable developer mode in ChatGPT, create a custom connector with your pinned AliasMode Remote MCP URL, and authenticate with OAuth. Browser tools load immediately; page actions start after a profile is selected.

OAuthConnector sign-in
BearerConnector tokens for API clients
Pinned URLOne device per connector

Set up ChatGPT

  1. Prepare the Windows host

    Install the Windows installer, choose Cloud mode, sign in, install CloakBrowser, and create at least one profile. Keep AliasMode running while ChatGPT works.

  2. Copy the pinned server URL

    Open Account & Settings, find Remote MCP, and copy the server URL for this exact device.

    https://cloud.aliasmode.com/v1/mcp/devices/<device-id>

  3. Enable developer mode in ChatGPT

    In ChatGPT settings, open Apps & Connectors and turn on developer mode under advanced settings. Developer mode enables creating custom MCP connectors.

  4. Create the connector with OAuth

    Create a custom connector, paste the pinned URL, and choose OAuth authentication with automatic client registration. Approve the AliasMode consent page with the account that owns the device.

  5. Or create a bearer connector

    For API and agent clients that use static credentials, create a connector token on the Windows host and configure the client to send it as Authorization: Bearer.

    cd "%LOCALAPPDATA%\AliasMode"
aliasmode-mcp remote-mcp create --name "ChatGPT"
aliasmode-mcp remote-mcp list

  6. Run a first task

    Select a profile, then let ChatGPT work:

    List my AliasMode profiles.
Open the profile named Research headless.
Take a page snapshot and summarize the page.
Close the browser.

Verify the connection

  • The connector shows as connected in ChatGPT and lists the AliasMode tools.
  • The tool list includes aliasmode_profiles_list plus 31 Playwright actions — 40 tools on the beta.47 installer.
  • Asking for profiles returns the roster of the Windows host, not another device.
  • A headless open plus browser_snapshot returns real page content from the host browser.
  • Closing the browser ends the session and the profile shows closed on the host.

Troubleshooting

SymptomFix
Creating the connector failsConfirm developer mode is on, paste the URL exactly as Account & Settings shows it, and retry. The host must be online and signed in during registration.
Tools appear but calls fail with an offline errorAliasMode is closed or the Windows machine is asleep. Reopen the app and keep the machine awake; remote clients cannot queue work for an offline device.
Some AliasMode tools are missing in ChatGPTChatGPT loads the tool list the connector advertises. beta.47 serves 40 tools; the previous beta.42 release served 39 aliasmode_profiles_replace_proxies. Reconnect the connector after updates.
Playwright actions return a selection errorOpen a profile or select an already-open browser first; lifecycle tools work without a selection, page actions do not.

What works over Remote MCP

  • Profile lifecycle: list, create, and delete profiles on the host
  • Browser control: open headful or headless, select an open browser, check status, capture and close safely
  • Page actions: the 31-tool Playwright set, from navigation and forms to screenshots, tracing, and verification
  • Bulk proxy replacement: aliasmode_profiles_replace_proxies on beta.47 source builds, dry-run first
See the full tool catalog

Local-only boundaries

ChatGPT reaches only the Remote MCP endpoint. It cannot touch the local stdio server on your machine and it cannot reach a host running in Local mode: remote connections require AliasMode Cloud and a signed-in Windows device.

  • No direct access to 127.0.0.1:50400 — the loopback Local API never leaves the host
  • No Local-mode hosts: sign the device in to Cloud before connecting web clients
  • No queueing: an offline device returns errors until it is back online
What the Local API does on the host Compare Local and Cloud modes

Sources and verification

  • OpenAI · Help Center — developer mode and custom connectors in ChatGPT (checked September 2026)
  • Model Context Protocol · MCP authorization specification — OAuth 2.1 flow used by remote servers (checked September 2026)
  • AliasMode repository · cloud-client.ts — pinned Remote MCP device URL format and connector management (checked September 2026)
  • AliasMode · Generated MCP tool catalog for the released 0.1.0-beta.47 installer (checked September 2026)

Public product details can change after the check date. Facts are re-checked on a monthly cycle.