Claude.ai connector

Run your AliasMode profiles from Claude.ai.

One pinned URL turns Claude.ai into a browser operator. Add the connector once, approve it with your AliasMode account, and Claude can open profiles and run Playwright actions on your Windows host.

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

Direct answer

Copy the pinned device URL from AliasMode Account & Settings, add it as a custom connector in Claude.ai with OAuth, and approve the consent page with the account that owns the Windows device.

OAuthWeb client sign-in
Pinned URLOne device per connector
PlaywrightPage actions

Set up Claude.ai

  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 Claude works.

  2. Copy the pinned server URL

    Open Account & Settings, find Remote MCP, and copy the server URL. It addresses this exact Windows installation and never redirects to another device.

    https://cloud.aliasmode.com/v1/mcp/devices/<device-id>
  3. Add a custom connector in Claude.ai

    Open Settings, choose Connectors, and add a custom connector. Paste the pinned URL and use OAuth with automatic client registration when the form asks.

  4. Sign in and allow access

    Claude opens the AliasMode consent page. Sign in with the same AliasMode account that owns the Windows device, then select Sign in and allow. The connector receives its own revocable OAuth grant — not the device credential.

  5. Select a profile and run actions

    Browser tools load with the connector, but page actions need a selected profile first:

    List my AliasMode profiles.
    Select the open profile named Research.
    Take a page snapshot and summarize the visible sections.
  6. Manage the connection

    Remove the connector in Claude.ai settings, revoke the device in AliasMode Cloud, or revoke connectors on the host to cut access at any time.

Verify the connection

  • The connector shows as connected in Claude.ai settings and lists the AliasMode tools.
  • 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.
  • GET /api/v1/status on the host at 127.0.0.1:50400 confirms the desktop app is healthy while a session runs.

Troubleshooting

SymptomFix
Adding the connector fails or times outConfirm the URL was copied exactly from Account & Settings on the host, that the host is online and signed in, then retry adding the connector.
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.
The consent page rejects the sign-inSign in with the AliasMode account that owns the Windows device, not a different workspace member.
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.

Endpoint reachability

Claude.ai connects from the public internet, so the Remote MCP endpoint must be reachable over HTTPS. The pinned cloud.aliasmode.com URL is that endpoint: AliasMode Cloud relays the session to your device, so the Windows host can stay behind NAT without tunnel software. The host itself must be online, signed in, and running AliasMode.

What Claude.ai can do

  • List and create profiles on the host, including temporary profiles
  • Open browsers headful or headless and select an already-open browser
  • Run the 31-tool Playwright set: navigate, click, type, fill forms, screenshot, verify, and trace
  • Capture and close browsers safely so cookies and session state return to the profile

Revoke and rotate access

Treat the connector like a team member with browser access. Remove it from Claude.ai when a project ends, revoke the device in AliasMode Cloud when hardware changes, and re-approve a fresh consent flow instead of sharing credentials.

Sources and verification

  • Anthropic · Claude Help Center — custom connectors and remote MCP (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 (checked September 2026)
  • AliasMode repository · mcp-tunnel.ts — Cloud relay that carries MCP sessions to the device (checked September 2026)

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