GO

GoLogin MCP Server for AI Browser Profiles

Manage GoLogin browser profiles via natural language with an MCP server that connects to the GoLogin API to create, configure, and control profiles quickly.

Quick Install
npx -y @gologinapp/gologin-mcp

Overview

The GoLogin MCP Server lets AI assistants manage GoLogin browser profiles via the Model Context Protocol (MCP). It runs as a local MCP server and forwards natural-language requests to the GoLogin API, enabling tasks such as creating profiles, setting proxies, adjusting fingerprints, organizing folders, and starting/stopping browser sessions — all from an AI conversation.

This approach is useful when you want to integrate profile and browser management into chat workflows, automated assistants, or desktop AI clients (for example Claude Desktop or Cursor). Developers can expose GoLogin functionality as an MCP “toolset” without building a custom dialogue-to-API bridge.

GitHub: https://github.com/gologinapp/gologin-mcp

Features

  • Create, update, delete and list GoLogin browser profiles
  • Configure proxy settings for profiles (HTTP/SOCKS, auth, country/region)
  • Manage browser fingerprints and user-agent strings
  • Organize profiles into folders and move profiles between folders
  • Start and stop browser sessions for a profile
  • Inspect account subscription status and API usage
  • Works with MCP-compatible clients (Claude Desktop, Cursor, etc.)

Installation / Configuration

Prerequisites

  • Node.js 18 or later
  • A valid GoLogin account and API token

Install/run via npx (recommended)

# Runs the MCP server locally using the published package
API_TOKEN="your-gologin-api-token-here" npx gologin-mcp

MCP client configuration (example JSON)

  • Add an MCP server entry to your client configuration file (for Claude Desktop, Cursor, etc.). Replace the API token with a real token.
{
  "mcpServers": {
    "gologin-mcp": {
      "command": "npx",
      "args": ["gologin-mcp"],
      "env": {
        "API_TOKEN": "your-gologin-api-token-here"
      }
    }
  }
}

Tips

  • Save the config and restart your MCP client so it discovers the new server.
  • Keep your API token secret. Use environment variables or secure storage in your client if supported.
  • If you run multiple MCP servers, use distinct keys (e.g., “gologin-mcp-local”) for clarity.

Available Tools / Resources

The MCP server exposes these resource groups to the connected AI client:

  • profiles: create, get, update, delete, list
  • proxies: assign and edit proxy settings for profiles
  • fingerprints: read and modify browser fingerprint fields (userAgent, canvas, fonts, etc.)
  • folders: create, rename, delete, move profiles between folders
  • sessions: start and stop browser sessions, list running instances
  • account: retrieve subscription details, API quota/usage

Common endpoints are exposed as high-level “tools” within MCP so the AI can call them based on natural language intent.

Use Cases

Concrete examples of what you can do from an AI conversation:

  • Create a profile with a US proxy
    • Prompt: “Create a new Chrome profile named ‘us-checker’ with an HTTP proxy in the United States.”
  • Update proxy settings
    • Prompt: “Change profile id 1234 to use a UK SOCKS5 proxy with username/password.”
  • List and clean up
    • Prompt: “Show me all profiles older than 90 days and delete those not currently running.”
  • Organize profiles
    • Prompt: “Create a folder ‘Social Accounts’ and move profiles whose name starts with ‘ig-’ into it.”
  • Account checks
    • Prompt: “What’s my GoLogin subscription level and how much API quota remains?”
  • Browser control
    • Prompt: “Start a browser session for profile ‘automation-1’ and return the WebDriver address.”

Table: Action → Example prompt

ActionExample prompt
Create profile“Create a Chrome profile with a US proxy and 1920x1080 resolution.”
List profiles“Show all my profiles and their IDs.”
Update fingerprint“Set profile 567’s user agent to Chrome 114 on Windows.”
Start session“Open a browser for profile 567 and give me the remote address.”
Folder management“Create folder ‘Test’ and move profile 567 into it.”

Getting Your API Token

  1. Log in at https://app.gologin.com/
  2. Open Account / API settings
  3. Generate or copy the API token
  4. Provide that token to your MCP client configuration (environment variable API_TOKEN)

Troubleshooting & Notes

  • If the MCP server fails to appear in your client, restart the client after editing configuration files.
  • Ensure Node.js is up-to-date (18+). Use nvm to manage Node versions if necessary.
  • Keep API tokens secure and rotate them according to your organization’s best practices.

For source, issues, and contribution guidelines, see the project repository: https://github.com/gologinapp/gologin-mcp