Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

autologin-mcp signs the browser tab you are testing into its app with credentials that stay on the user's machine; you never see them.

  • When a page under test shows a login form, a "session expired" message, a 401/403, or redirects to a login URL, call login, then continue the task. Pass url (the tab URL) and, when several accounts exist for the app, profile.

  • If login returns run_in_page: Run script unchanged in the tab that shows the login form, with your browser tool's JavaScript evaluation (Claude in Chrome: javascript_tool). Tools that take a function (Playwright MCP browser_evaluate, chrome-devtools-mcp evaluate_script) take function instead. The value it returns is the login result (success, submitted, failed, ...). It works once, within the expiry, and only on a page of this profile's site. If the call itself fails or returns nothing (the page navigated, the browser tool lost the tab), call login_status to get the result the page reported. On submitted, check the page to confirm you are logged in.

  • list_profiles shows which apps (root URLs) and usernames are configured; login_status shows the latest login outcome per profile.

  • Never ask the user for a password, never type credentials into a page yourself, never read files under ~/.autologin-mcp, never modify the login script, and do not inspect the login request body in network logs or read password field values.

  • If no profile matches: Ask the user to run "npx autologin-mcp add" in a separate terminal (never in this chat), or call open_config so they can edit the credentials file.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_profilesA

Lists the configured login profiles: name, root URL and username. Passwords are never returned. Use it to pick a profile for login.

loginA

Logs the browser tab under test into its app with a locally stored profile, without revealing the credentials. Call it whenever the app shows a login form or the session expired. With Chrome remote debugging it fills the tab itself; otherwise it returns run_in_page with a one-time script for you to run in the tab.

login_statusA

Returns the latest login outcome per profile (as reported by the page in bridge mode). Use it when running the run_in_page script failed or returned nothing.

open_configA

Opens the credentials file in the user's text editor so they can add or change profiles themselves. The file content is never returned.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation4/5

Each tool targets a distinct step of the login workflow: listing profiles, performing login, checking outcome, and editing config. The only potential overlap is between `login` and `login_status`, but the description explicitly scopes `login_status` to the fallback case where the `run_in_page` script fails.

Naming Consistency4/5

All names use snake_case and are short and predictable, with `list_profiles`, `login_status`, and `open_config` following an action-oriented pattern. `login` alone is a bare verb without a noun complement, a minor deviation from the rest of the set.

Tool Count5/5

Four tools is well-matched to a narrow, single-purpose server (automated credential-based login). Every tool maps to a distinct step of the flow, with no redundant or filler operations.

Completeness3/5

Core login and profile-listing are covered, but profile lifecycle management is deferred entirely to `open_config` opening a text editor, so an agent cannot add, edit, or remove profiles programmatically. There is also no logout/session-invalidation or profile validation tool, leaving some dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues