GoLogin MCP Server is a Model Context Protocol (MCP) server for AI agents, used to manage GoLogin browser profiles, proxies, fingerprints, folders, and cloud browser sessions through AI conversations. It connects AI clients to the GoLogin API, enabling users to operate GoLogin's various features in natural language.

Purpose

The main purpose of this server is to enable AI clients (such as Claude Desktop, Cursor, and other clients that support local stdio MCP servers) to directly manage browser profiles and related resources in a GoLogin account. Through conversation, users can complete create, read, update, and delete operations on profiles, proxy settings, fingerprint refresh, folder management, account information reading, and starting and stopping cloud browser sessions.

Main Capabilities

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, clicking, form filling, or local Orbita launch tools. For page automation, use a separate browser automation client or the GoLogin Agent Browser CLI.

Usage

Prerequisites

Requires Node.js 22 or later, a valid GoLogin account, and a GoLogin API token. Node.js 22 and 24 LTS have been tested on macOS Apple Silicon.

Get an API Token

Configure the MCP Client

Add the following configuration to your MCP client, replace the token placeholder, and merge it into your existing mcpServers configuration. Restart or reload the client's MCP connection, then you can ask: "Show me my GoLogin profiles." The client will automatically start the server. -y lets npm install the package without interactive confirmation. This server reads API_TOKEN; other GoLogin CLI's GOLOGIN_TOKEN variable is not an alias here.

Terminal Startup Check

With API_TOKEN already set in the environment, you can perform a terminal startup check. The server communicates via standard input/output (stdio) and waits for an MCP client. It does not itself open a browser or provide an interactive command prompt.

Tool Calls

Tool names are generated from the HTTP methods and paths in the GoLogin OpenAPI specification, which the server loads at startup. The following are some of the available tools, not a fixed alias list. You can query tools/list in the MCP client to get the current names and input schemas. For example, an MCP client can send a tools/call request to read a profile. Parameters follow each tool's input schema. Path and query parameters and request body fields are passed as top-level parameters.

Example Prompts

"Show me my GoLogin profiles."
"Create a Linux profile named 'Research'."
"Rename profile PROFILE_ID to 'Research US'."
"Update profile PROFILE_ID to use these proxy settings."
"Refresh the fingerprint for profile PROFILE_ID."
"Create a folder named 'Research' and add profile PROFILE_ID to it."
"Start profile PROFILE_ID in the cloud and give me the connection URL."
"Stop the cloud session for profile PROFILE_ID."
"Show my GoLogin account information."

Setup for Each MCP Client

Claude Desktop: Open Settings > Developer > Edit Config, and add the quick start configuration to claude_desktop_config.json. Fully quit and restart Claude Desktop, then check whether gologin-mcp and its tools are available.
Cursor: Add the quick start configuration to the user account's ~/.cursor/mcp.json, or the project's .cursor/mcp.json. Reload the MCP connection and enable the server's tools. Configurations containing API tokens should be kept out of version control.
Other MCP clients: Use a client that supports local stdio MCP servers. Configure the command as npx, with arguments -y and gologin-mcp, and set API_TOKEN in the server environment. The configuration format and location depend on the client.

When to use

Suitable for users who need to manage GoLogin browser profiles, proxies, fingerprints, and cloud sessions in bulk or conveniently through AI conversations, especially in scenarios using MCP-capable AI clients such as Claude Desktop and Cursor.

Limitations

Requires Node.js 22 or later, a valid GoLogin account, and an API token.
The MCP process runs locally; GoLogin API requests and cloud browser sessions require network access.
Cloud availability and API operations depend on account permissions and plan.
The server needs access to docs-download.gologin.com to load tool definitions.
No page navigation, clicking, form filling, or local Orbita launch tools are provided.
Tool names are not fixed aliases; the current names must be obtained via tools/list.
Local MCP startup itself does not launch Orbita on the computer.

Troubleshooting

Server not connected: Check whether the client has Node.js and npx available, then restart its MCP connection. The server also needs access to docs-download.gologin.com to load tool definitions.
API returns 401 Unauthorized: Check the API_TOKEN passed to the server and its validity in GoLogin. Restart the connection after changes.
Tool names not found: Refresh the tool list and use the names returned by tools/list; names such as list_profiles and start_browser are not built-in aliases.
Cloud launch fails: Check the API response and the account's cloud access permissions.

Publishing and registration

This package contains only the built server, package metadata, README, and license. The publish check verifies this allowlist to ensure that local state, databases, credentials, and development files are not included as extra files. npm publish automatically runs the same check. server.json describes this server under the official MCP Registry as io.github.gologinapp/gologin-mcp. The npm package declares the same identifier in mcpName. The versions in package.json, package-lock.json, and server.json must be kept consistent. First publish the checked npm package, then run Publish to MCP Registry from the main branch in the repository's Actions tab. This workflow verifies that the npm release contains the correct Registry identifier and authenticates using GitHub OIDC, without requiring a separate Registry token. It does not publish to npm.

gologin-mcp

About this tool