Skip to main content
Glama
ZennoBrowser MCP Server

ZennoBrowser MCP Server

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ZB_API_TOKENYesAuthentication token for the ZennoBrowser Public API
ZB_API_BASE_URLNoBase URL of the ZennoBrowser Public APIhttp://localhost:8160

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_workspacesA

The operation retrieves the list of workspaces accessible to the current user. This information is required to execute most subsequent queries.

get_proxiesA

This method provides functionality for filtering, sorting, and paginating proxies. It can filter results by workspace ID, folder ID, proxy ID, name, and sorting criteria. If parameters are not specified, the response returns the default page of proxies in standard order.

create_proxyB

This method is used to add a new proxy entry using the provided configuration parameters. It returns the generated unique identifier.

bulk_create_proxyA

This method processes an array of proxy data and creates all specified proxies. Errors during creation of individual proxies are ignored.

update_proxyB

This method modifies configuration of an existing proxy server based on specified parameters. Any parameters set to null will leave the corresponding property of the proxy unchanged.

delete_proxyB

This method deletes a proxy from the list by the specified ID. The proxyId value must match an existing proxy in the specified workspace.

bulk_delete_proxyB

This method sends a bulk delete request to the API to remove the specified proxies. Ensure that the provided proxy IDs are valid and exist in the specified workspace.

change_mobile_proxy_ipA

This endpoint triggers an IP change for the specified mobile proxy. The proxy must have a valid IP change URL configured.

get_proxy_foldersA

This method is used to get the list of proxy folders. It supports filtering, sorting, and pagination in returned results. Optional query parameters can be used to refine the result set. If parameters are not specified, the method returns the first page of proxy folders in the default sorting order.

create_proxy_folderA

This method creates a new proxy folder. The caller must ensure that the specified workspace ID and location are valid. Proxy folder is container for proxies and is used for better organization. Each folder has a unique identifier that is returned upon creation and can be used for subsequent operations on the folder, such as updating or deleting.

update_proxy_folderB

This method updates the name of the specified proxy folder. This is the only editable property.

delete_proxy_folderB

This method deletes a proxy folder. The parameter proxyFolderId must match the existing folder within the specified workspace.

delete_proxy_folder_with_contentsA

This method deletes a proxy folder and all proxies it contains. The parameter proxyFolderId must match the existing folder within the specified workspace.

get_profile_foldersA

This method retrieves a list of folders available in the specified workspace. Optionally, it is possible to limit the number of results, specify filters, or define sorting conditions. If no parameters are specified, the method returns the first page of profile folders in the default order.

create_profile_folderA

This method creates a profile folder. The caller must ensure that the specified workspace ID and location are valid. Profile folders are contained within workspaces and can be used to organize browser profiles. Each folder has a unique identifier, a name, a location (Local or Cloud), and a quantity representing the number of profiles it contains. Profile folders count is limited by tariff.

update_profile_folderC

This method can be used to update the profile folder name.

delete_profile_folderC

This method is used for deleting a profile folder. The profileFolderId value must match the existing folder in the specified workspace.

delete_profile_folder_with_contentsA

This method deletes a profile folder and all profiles it contains. The profileFolderId value must match the existing folder in the specified workspace.

get_profilesA

This method retrieves a list of profiles with their attributes from the specified workspace and the folder. It is possible to optionally filter results by ID, name, tags, and sorting.

create_profileB

This method creates a new browser profile in the specified workspace and the folder. It is possible to customize various parameters such as screen size, hardware emulation, language, timezone, proxy, and others. All parameters are optional if another is not specified. Browser profile is a set of parameters for browser configuration that can be used to create browser instances with different fingerprints and settings. Each profile has a unique identifier that is returned upon creation and can be used for subsequent operations on the profile, such as updating or deleting.

bulk_create_profileC

This method is used to create new multiple browser profiles in the specified workspace and the folder. Each profile can have its own configuration, including screen size, hardware emulation, language, timezone, proxy, and other parameters. All fields are optional if another is not specified.

update_profileC

This method updates an existing browser profile.

delete_profileC

This method deletes an existing browser profile.

bulk_delete_profileC

This method is used to delete several existing browser profiles at once.

import_cookiesB

This method allows importing cookies into an existing profile in JSON format. Ensure that the cookies parameter is a valid JSON value representing the cookies to be imported. Cookies will overwrite existing cookies in the profile.

export_cookiesB

This method allows exporting cookies from an existing profile in JSON format. The exported cookies can be used for backup or transfer purposes.

copy_cookiesA

Copies cookies from source profile to target profile. Cookies in the target profile will be overwritten.

get_profileC

Retrieves detailed information about a specific Browser Profile

recover_profileA

This method can be used to recover a browser profile that is in an invalid state in the specified workspace. Most common use case is to recover a profile that is crashed or corrupted due to a machine failure.

force_unlock_profileA

This method can be used to force unlock a cloud browser profile that is currently locked by another machine in the specified workspace.

cleanup_profileB

This method can be used to clean up cached data for a browser profile in the specified workspace.

move_profileB

This method moves one or more browser profiles to the specified target folder within the workspace.

bulk_update_profile_presetC

This method updates the preset configuration for one or more browser profiles at once.

bulk_update_profile_proxyB

This method updates the proxy settings for one or more browser profiles at once. You can either set a specific proxy server or assign proxies from a container.

bulk_update_profile_tagsC

This method updates the tags for one or more browser profiles at once.

run_cookie_robotB

This method starts the cookie robot for the specified browser profiles. The robot opens each profile's browser and visits the provided URLs to collect cookies.

get_script_run_statusC

Retrieves per-profile status of a previously started script run.

get_extensionsC

Retrieves extensions accessible to the current user.

create_extension_from_webC

Adds a web extension to the specified preset.

create_extension_from_fileC

Adds a file extension to the specified preset.

delete_extensionC

Deletes an extension.

get_presetsC

Retrieves presets accessible to the current user.

create_presetA

Creates a new preset. Presets are used to group extensions, bookmarks, manage them together and assign them to profiles. All presets are cloud-based.

delete_presetC

Deletes a preset.

get_threadsC

This method retrieves the list of execution threads for the specified workspace. Threads can be filtered by token or type, limited by the number of results, and sorted using the provided parameters.

create_threadA

This method runs a new execution thread in the specified workspace. Execution threads are used to start, work with a browser instance. They can be manually continued with the continue_use_thread method or stopped with the stop_thread method.

bulk_create_threadB

This method can be used to start execution threads in bulk for the specified workspace.

continue_use_threadC

This method is used to continue work of the execution thread associated with the thread token.

bulk_continue_use_threadB

This method is used to update the specified execution threads, allowing them to continue working. The threadTokens parameter should contain the array of valid tokens with existing workspace IDs.

stop_threadA

This method can be used to stop an existing execution thread. Stopping a thread will also stop the associated browser instance, if it exists.

bulk_stop_threadC

This method stops multiple execution threads.

get_browser_instancesA

This method returns the list of browser processes available for the current user with detailed information. Results can be filtered by profile ID or process ID, optionally sorted, and limited by the number of returned entries. Important: these actions are applied only to browser instances launched via the API.

start_browser_instanceC

This method creates the new browser instance using the specified profile with optional workspace and desktop settings.

get_running_browser_instanceC

Throws if no browser instance is currently running for the given profile.

bulk_start_browser_instanceB

This method is used to create browser instances in bulk for the specified profiles. Ensure that the provided profile IDs are valid and that the specified workspace ID exists.

stop_browser_instanceA

This method stops the existing browser instance associated with the specified profile. This operation permanently closes the browser instance and releases all associated resources.

bulk_stop_browser_instanceA

This method stops multiple existing browser instances associated with the specified profiles. This operation permanently closes all specified browser instances and releases their resources.

focus_browser_instanceC

Bring the browser window of the specified profile to the foreground

set_browser_instance_visibilityA

Set browser instance window visibility (show or hide). This method works only for browser instances launched via the API with reveal or conceal options.

get_product_versionC

This method returns the current version of the product.

get_browser_versionB

This method returns the current version of the browser engine.

get_limitsC

This method returns the current limits for the specified workspace.

get_tariffB

This method returns the current tariff for the specified workspace.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 63 tools

Disambiguation3/5

Core resources are separated (profiles, proxies, folders, threads, browser instances), but boundaries blur between create_thread/start_browser_instance and between update_profile and bulk_update_profile_proxy/tags. Bulk prefixes help, yet an agent must still decide whether to operate on threads or browser instances to open a browser.

Naming Consistency5/5

All names use snake_case and almost all follow a verb_noun form (get_profiles, create_proxy, bulk_delete_profile, stop_thread). Variants like change_mobile_proxy_ip and get_running_browser_instance are more specific but still fit the same readable pattern.

Tool Count1/5

63 tools is far beyond the 3-15 well-scoped range and exceeds the 50+ extreme threshold, including many single/bulk CRUD pairs and ancillary endpoints. While the platform is broad, this surface imposes heavy selection and context overhead.

Completeness3/5

Major entities have CRUD/lifecycle coverage, including bulk operations. However presets lack update_preset/get_preset, extensions lack update, and get_script_run_status has no corresponding script-run/start tool, leaving notable dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues