autologin-mcp

Agents and browser tools

autologin-mcp does not drive the browser for your tests. The agent keeps using the browser tool it already has; autologin-mcp only handles the login. Two things matter:

  1. The agent must be an MCP client, so it can call login.
  2. The browser tool must be able to run JavaScript in the tab (bridge mode), or the tab must live in a Chrome that autologin-mcp can reach over CDP (CDP mode).

Claude Code + Claude in Chrome

This is the primary setup, tested end to end on real apps.

Claude Code + Playwright MCP

Claude Code + chrome-devtools-mcp

Other MCP clients

The server itself is a standard stdio MCP server, so other clients can start it. Register it with your client’s MCP configuration, for example in the common mcpServers JSON format:

{
  "mcpServers": {
    "autologin": { "command": "npx", "args": ["-y", "autologin-mcp@1.0.1"] }
  }
}

Then add profiles with npx autologin-mcp add. Keep in mind:

Browsers

Edit this page on GitHub