MCP Login Server
Provides automated login functionality for OrangeHRM systems, offering tools to perform login operations with predefined credentials, test connectivity to the target system, and retrieve login credentials for verification.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Login Server log me into the localhost application"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Login Server
A Model Context Protocol (MCP) server that provides automated login functionality for http://localhost using predefined credentials. This server is designed to work with browser automation tools like the Playwright MCP server.
Features
Automated Login: Provides tools to perform login operations with predefined credentials
Playwright Integration: Designed to work with the Playwright MCP server for browser automation
Connection Testing: Includes tools to test connectivity to the target URL
Credential Management: Secure handling of login credentials
Extensible Architecture: Easy to add new tools with separated tool definitions
Related MCP server: hap-oauth-mcp
Project Structure
src/
├── index.ts # Main server setup and entry point
├── tools.ts # Tool definitions and registration
└── index.js # Compiled JavaScript (auto-generated)The codebase is structured for easy extensibility:
index.ts: Contains the main server setup, startup logic, and process managementtools.ts: Contains all tool definitions, registration functions, and configurationADDING_TOOLS.md: Detailed guide for adding new tools to the server
Installation
npm install
npm run buildUsage
Running the Server
npm startOr for development:
npm run devAvailable Tools
The server provides the following MCP tools:
perform_login - Performs automated login to http://localhost using predefined credentials
get_login_credentials - Returns the login credentials for verification
test_connection - Tests if the target URL is accessible
Configuration
The server is configured with the following credentials:
Target URL:
http://localhostUsername:
adminPassword:
AIWorkshopJuly!25
These credentials are configured for the OrangeHRM system running on localhost.
MCP Configuration
To use this server with an MCP client (like Claude for Desktop), add the following configuration:
Windows
{
"mcpServers": {
"login-server": {
"command": "node",
"args": ["C:\\ABSOLUTE\\PATH\\TO\\PROJECT\\build\\index.js"]
}
}
}macOS/Linux
{
"mcpServers": {
"login-server": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/PROJECT/build/index.js"]
}
}
}Integration with Playwright MCP Server
This server is designed to work alongside the Playwright MCP server for complete browser automation. The perform_login tool provides the necessary information and steps that can be executed by the Playwright MCP server.
Example Workflow
Use the
test_connectiontool to verify the target URL is accessibleUse the
perform_logintool to get login instructionsUse Playwright MCP server tools to execute the browser automation steps
Development
Project Structure
src/
├── index.ts # Main server implementation
├── types.ts # TypeScript type definitions (if any)
build/ # Compiled JavaScript output
.github/ # GitHub configuration
├── copilot-instructions.md # Copilot development guidelinesBuilding
npm run buildScripts
npm run build- Compile TypeScript to JavaScriptnpm start- Run the compiled servernpm run dev- Build and run in development modenpm run clean- Clean build directory
Dependencies
@modelcontextprotocol/sdk- MCP SDK for TypeScriptzod- Runtime type validationtypescript- TypeScript compiler
Error Handling
The server includes comprehensive error handling for:
Connection failures
Invalid credentials
Network timeouts
MCP protocol errors
Security
Credentials are stored as constants in the code
No sensitive data is logged to stdout (only to stderr for debugging)
Connection testing uses safe HTTP HEAD requests
Contributing
Fork the repository
Create a feature branch
Make your changes
Test thoroughly
Submit a pull request
License
ISC License
Available Tools
4 toolsget_login_credentialsB
Returns the login credentials that will be used for authentication to http://localhost
Inputs: no named parameters.
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.
Inputs: url.
test_connectionA
Tests if the target URL (http://localhost) is accessible
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Plausible MCP server for ChatGPT, Claude and any AI agent: list sites, get site stats, get top pages, get traffic sources, create site, add goal, create shared link and invite guest in your own Plausible account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Plausible yourself; Cotlet does not store your password and you need no Plausible API key. About the official Plausible API: Plausible has an official API, but a limited one (checked 22 Oct 2026). The Stats API only reads data and needs the Business plan, the Sites API that creates sites, goals and shared links is Enterprise only, and there is no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/plausible-api-mcp-server
LearnUpon MCP server for ChatGPT, Claude and any AI agent: list users, invite users, add users to group, enroll group on course, enroll users on course, unenroll users, set enrollment complete and disable user in your own LearnUpon account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to LearnUpon yourself; Cotlet does not store your password and you need no LearnUpon API key. About the official LearnUpon API: LearnUpon has a REST API and a reporting MCP server, but neither covers day-to-day admin work from an AI agent (checked 20 Oct 2026). The REST API uses API keys that an admin generates under Settings > Integrations > API Keys, and Support grants them when the option is missing. Setup and FAQ: https://cotlet.dev/integrations/learnupon-api-mcp-server
AppFolio MCP server for ChatGPT, Claude and any AI agent: create work order, assign work order, schedule work order, list open work orders, get tenant ledger and run report in your own AppFolio account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to AppFolio yourself; Cotlet does not store your password and you need no AppFolio API key. About the official AppFolio API: Partly. AppFolio announced a Realm-X connector for Claude on 9 Jun 2026, which hands a job to Realm-X inside AppFolio, and its pricing page lists an AppFolio API on the Plus (read only) and Max (read/write) plans (checked 6 Nov 2026). Setup and FAQ: https://cotlet.dev/integrations/appfolio-api-mcp-server
Findymail MCP server for ChatGPT, Claude and any AI agent: find email, verify email, start lead search, add excluded domains, list contact lists and get credits in your own Findymail account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Findymail yourself; Cotlet does not store your password and you need no Findymail API key. About the official Findymail API: Findymail has a full REST API with a Bearer key, but no first-party MCP server (checked 23 Oct 2026). Its API docs cover the email finder and verifier, contact lists, exclusion lists, Intellimatch lead search, Signals and credits, and mention no MCP. Setup and FAQ: https://cotlet.dev/integrations/findymail-api-mcp-server
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables automated GitHub login through browser automation using Playwright. Provides MCP tools for programmatic authentication to GitHub accounts with credential management.1-
- AlicenseNot gradedqualityDmaintenanceProvides automated login and credential refreshing for Mingdao (HAP) using Playwright to extract session tokens and cookies. It enables AI tools to maintain authenticated access to Mingdao Cloud for automation scripts and MCP configurations.MIT
- AlicenseNot gradedqualityDmaintenanceEnables secure remote access to a Playwright-based MCP server with authentication and role-based access control powered by Descope.ISC
- AlicenseBqualityCmaintenanceMCP server for secure credential management, browser-based login automation, and TOTP/2FA auto-solving. Encrypts credentials with AES-256-GCM and automates login flows via Playwright.322MIT