MCP Login Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| perform_loginA | Performs automated login to http://localhost using predefined credentials (admin/AIWorkshopJuly!25). This tool requires a Playwright MCP server to be running for browser automation. |
| get_login_credentialsB | Returns the login credentials that will be used for authentication to http://localhost |
| test_connectionA | Tests if the target URL (http://localhost) is accessible |
| navigate_to_pimA | Navigates to the PIM (Personal Information Management) page using the left-hand navigation menu. Assumes user is already logged in. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get_login_credentials retrieves stored credentials, perform_login executes the login process, navigate_to_pim handles post-login navigation, and test_connection checks URL accessibility. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern (get_login_credentials, navigate_to_pim, perform_login, test_connection) with clear, descriptive names that uniformly use snake_case. No deviations or mixed conventions are present.
With 4 tools, this server is well-scoped for its login automation purpose. Each tool earns its place by covering distinct aspects: credential management, login execution, navigation, and connectivity testing, without being overly sparse or bloated.
The tool set covers core login workflows (testing, credential retrieval, login, post-login navigation) effectively. A minor gap exists in logout functionality, but agents can work around this, and the surface is largely complete for the stated domain.