login-mcp
Related Servers
Alternatives to login-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and terminal users to control a logged-in Chrome browser, performing actions like opening pages, searching, filling forms, and taking screenshots without re-authentication.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to drive a headless Chrome browser that is already logged in to the user's accounts, supporting multiple accounts and safe handling of Google sessions without manual login or 2FA.MIT
- AlicenseAqualityCmaintenanceEnables agents to sign into websites through a real browser without exposing passwords, keeping cookies in a local Chrome profile and providing tools for browsing and managing authenticated sessions.51MIT

Wbrowserofficial
AlicenseNot gradedqualityAmaintenanceEnables AI assistants and terminals to control a user's already logged-in Chrome session, allowing them to navigate pages, read content, click and type, run JavaScript, and inspect console or network activity.30MIT- AlicenseNot gradedqualityBmaintenanceEnables controlling an existing logged-in Chrome session through MCP, including page reading, DOM interaction, tab management, and allowed file upload/download with local security boundaries.MIT
- AlicenseAqualityDmaintenanceEnables AI agents to control the user's Chrome or Firefox browser, leveraging existing sessions for tasks requiring authentication and user handoff.1859 npm19MIT
TDQS
Scored across 6 tools
auth_login (human-driven login window) and auth_open (agent-driven navigation in a confirmed profile) both open Chrome, which could cause confusion, but their descriptions clearly delineate human login vs. agent browsing. auth_read and auth_act are cleanly separated by read vs. interaction, and auth_status is distinct.
All six tools use the consistent auth_ verb_noun pattern (auth_login, auth_confirm, auth_open, auth_read, auth_act, auth_status). Names are predictable and map cleanly to actions.
Six tools is well-scoped for an authenticated-browsing server: setup (login, confirm), operations (open, read, act), and introspection (status). Each tool earns its place with no redundancy.
The surface covers the full login-to-automation lifecycle including origin confirmation and status reporting, with sensible safety boundaries. Session teardown/logout or multi-step action batching are minor gaps an agent can work around.