Skip to main content
Glama
Sign In
hotlogin-mcp

hotlogin-mcp

by hotlogin-browser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to hotlogin-mcp

No user-submitted related servers found.

    Related Servers

    • MultiZen

      EmmaRiley1169
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that exposes browser-drive tools over a local endpoint, letting AI agents launch and control isolated browser profiles with their own cookies, fingerprints, and proxies, then navigate, click, type, extract, screenshot, evaluate JS, and manage tabs and cookies. Session state persists across launches so authenticated workflows carry over between AI sessions.
      MIT

    • rata-mcp

      fuhidev
      A
      license
      B
      quality
      C
      maintenance
      This MCP server connects AI agents to antidetect browser profiles. It enables vision-based element interaction and complex automated workflows within the RATA/GHM Automate v2 ecosystem.
      6
      341 npm
      MIT

    • MCP Browser

      wgarrido
      A
      license
      A
      quality
      D
      maintenance
      MCP server that lets AI assistants browse the web through your real Chrome with your cookies, sessions, and fingerprint, avoiding bot detection and CAPTCHAs. Enables web browsing, content extraction, and multi-step workflows via persistent tabs.
      15
      11 npm
      3
      MIT

    • browser-store

      bysking
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing and controlling multiple isolated Chrome/Edge browser instances, exposing tools for navigation, screenshots, clicking, form filling, and JavaScript execution to AI clients.
      7 npm
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    C2.7/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource type (env, group, proxy, health) and specific actions (create, query, remove, revise, etc.), making it easy for an agent to select the right tool without confusion.

    Naming Consistency5/5

    Tool names follow a highly consistent pattern throughout: resource_action format (e.g., env_create, group_query, proxy_remove). All tools use snake_case with no deviations, and verbs are standardized across resources, ensuring predictable naming.

    Tool Count4/5

    With 23 tools, the count is slightly high but reasonable for the server's scope of managing environments, groups, and proxies. Each tool appears to earn its place by covering specific operations, though it may feel heavy compared to simpler servers.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for environments, groups, and proxies, including additional operations like launching, terminating, and checking health. There are no obvious gaps, and agents can handle full workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources