gologinapp/gologin-mcp

Manage GoLogin browser profiles, proxies, fingerprints, folders, and cloud browser sessions through AI conversations. This Model Context Protocol (MCP) server connects your AI client to the GoLogin API.
Quickstart
You need Node.js 22 or newer, an active GoLogin account, and a GoLogin API token. Node.js 22 and 24 LTS have been tested on macOS Apple Silicon.
1. Sign in to your GoLogin account, open **API & MCP**, and generate a token in the **API** tab.
2. Add this configuration to your MCP client, replacing the token placeholder. Merge it into any existing mcpServers configuration.
3. Restart or reload your client's MCP connection, then ask: **"Show me my GoLogin profiles."**
The client starts the server automatically. -y lets npm install the package without an interactive confirmation. This server reads API_TOKEN; the GOLOGIN_TOKEN variable used by other GoLogin CLIs is not an alias here.
For a terminal startup check, with API_TOKEN already set in your environment:
The server communicates over standard input/output (stdio) and waits for an MCP client. It does not open a browser or provide an interactive command prompt by itself.
What You Can Do
- Create, read, update, delete, and organize browser profiles.
- Configure profile proxies and refresh browser fingerprints.
- Manage folders and their profile membership.
- Read account information.
- Start and stop browser profiles in the GoLogin cloud.
Cloud startup returns a connection URL. This server does not expose page navigation, click, form-filling, or local Orbita launch tools. For page automation, use a separate browser automation client or the GoLogin Agent Browser CLI.
The MCP process runs locally; GoLogin API requests and cloud browser sessions require network access. Cloud availability and API operations depend on your account permissions and plan.
Tools
Tool names are generated from the HTTP method and path in the GoLogin OpenAPI specification, which the server loads at startup. The following is a selection of available tools, not a fixed list of aliases. Query tools/list in your MCP client for the current names and input schemas.
| Tool | Description |
| --- | --- |
| get_profile_v2 | List and search profiles, with pagination and folder filters |
| post_profile_custom | Create a profile with partial settings such as name, OS, and proxy |
| get_profile_id | Read a profile by ID |
| put_profile_id_custom | Update selected profile settings |
| delete_profile | Delete the profiles listed in profilesToDelete |
| patch_profile_proxy_many_v2 | Configure proxies for one or more profiles |
| patch_profile_fingerprints | Refresh fingerprints for the profiles listed in browsersIds |
| get_proxy_v2 | List proxies |
| get_folders | List folders |
| post_folders_folder | Create a folder by name |
| patch_folders_folder | Add or remove profiles from a folder |
| delete_folders_folder | Delete a folder by name |
| post_profile_id_web | Start a profile in the cloud and return a connection URL |
| delete_profile_id_web | Stop a cloud profile |
| get_user | Read account information |
For example, an MCP client can send this tools/call request to read a profile:
Arguments follow each tool's input schema. Path and query parameters, and request body fields, are passed as top-level arguments.