# MCP Overview

With MoreLogin MCP (Model Context Protocol), you can control MoreLogin directly from AI tools (such as Claude, Cursor) using **natural language conversation**, enabling automation without writing a single line of code.

## Overview

**Who is it for?**
AI developers, prompt engineers, and users of LLM tools (like Cursor, Claude) who want to instruct AI agents to perform browser tasks on their behalf.

**What can it do?**

- **Browser Profile Management**: Instruct the AI to create, start, close, or delete profiles.
- **In-Page Automation**: Tell the AI to visit web pages, type text, click elements, extract data, or take screenshots in an open profile.


**Supported AI Tools (Clients)**
Any tool that supports the Model Context Protocol (MCP) as a client can connect to the MoreLogin MCP server. Verified tools include:

- **Cursor** (AI Code Editor)
- **Claude Desktop** (Anthropic's Desktop App)
- **Claude Code** (Anthropic's CLI Agent)
- **Cline / Roo Code** (VS Code extensions)


## Permissions & Security

The MCP server runs locally on your machine alongside the MoreLogin desktop client.

- **Local Control Only**: The MCP server only executes commands on your local MoreLogin client. It does not expose your browser profiles to the public internet.
- **Agent Authority**: When you connect an AI agent to the MCP server, the agent gains the ability to create, modify, and delete local profiles, as well as interact with active webpages. Always review the actions proposed by the AI before approving them.


## Configuration Fields Explained

When you copy the MCP configuration from the MoreLogin client, it typically contains the following fields:

- **`command`**: The executable that runs the MCP server (e.g., `node` or the path to a bundled executable).
- **`args`**: The arguments passed to the command, which specify the path to the MCP server script and any necessary flags.
- **`env`** (Optional): Environment variables required for the server to authenticate with your local MoreLogin client instance (like local API ports or tokens).


## Capabilities Mapping (Exposed Tools)

Once configured, the MCP server exposes specific "tools" to the AI agent. The AI will automatically select the right tool based on your natural language prompt.

| Category | Example Tools Available to AI |
|  --- | --- |
| **Profile Management** | `create_profile`, `start_profile`, `close_profile`, `delete_profile` |
| **In-Page Automation** | `visit_url`, `click_element`, `type_text`, `evaluate_js`, `screenshot` |


## Troubleshooting

- **Server Not Found / Connection Refused**: Ensure the MoreLogin desktop client (v2.50.0+) is currently running. The MCP server relies on the local MoreLogin application.
- **Tool Execution Failed**: If an AI agent fails to execute an in-page action (like `click_element`), the element might not be fully loaded. Ask the AI to wait a few seconds or use a broader selector.
- **Configuration Missing**: If you restarted your PC, make sure MoreLogin is launched *before* you prompt your AI agent, so the MCP connection can be established.


## Quick Setup Guides

Choose your AI Agent below for detailed setup instructions:

- **[Cursor Setup Guide](/mcp/cursor)**
- **[Claude Desktop Setup Guide](/mcp/claude-desktop)**
- **[CLI Agents (Claude Code, Cline) Setup Guide](/mcp/cli-agents)**


# Adaptive AI Engine (Optional)

When automation flows are complex or page structure changes and breaks existing flows, you can configure an AI model and enable the adaptive engine. It adjusts the strategy in real time and adapts to page changes so automation stays reliable.

> **Use when**: page structure changes often, there are many dynamic elements, or you need flexible handling of edge cases.


![Adaptive AI Engine](/assets/image12.ba6f4e786bb1900f8aa72ff1e08bbc73cc273f99d1c4a4b8aef970bd99fd7e3a.0feb6212.png)