Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

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

Cross-browser data tools: read/write/sync cookies, passwords, bookmarks and local/session storage across installed browsers (chrome, yandex, chromium, safari, obscura).

Security policy:

  • sync_data/export_state move secret VALUES inside this process only and return counters — never paste cookies/passwords into the conversation.

  • get_cookies/get_credentials/get_site_storage return values ONLY when reveal=True is passed explicitly. Otherwise metadata with masked values.

  • Write tools (set_*, sync_data with dry_run=False, import_state, add_bookmark) must be called ONLY on the user's explicit request.

Gotchas:

  • Most file-level writes require the target browser to be QUIT (sqlite locks, Bookmarks/Cookies clobbered on exit) — errors will say so.

  • Safari file access needs Full Disk Access for the host app; without it the tools return an FDA-needed error. Safari passwords are per-site only.

  • obscura keeps data in memory of a spawned child process — state is ephemeral and unrelated to any other obscura MCP instance.

  • Syncing live login sessions copies refresh tokens; two browsers sharing one account will invalidate each other on token rotation.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_browsersA

Detected browsers: profile paths, running state, CDP/file access and per-kind capabilities (read/write flags).

get_cookiesA

Cookies for a browser, optionally filtered by domain suffix. Without reveal=True the value field is masked.

set_cookiesA

Write cookies into a browser's jar. ONLY on explicit user request. Each item: {name, value, domain, path?, expires?, secure?, http_only?, same_site?}.

list_bookmarksD

All bookmarks with folder paths.

add_bookmarkB

Add one bookmark. ONLY on explicit user request.

get_credentialsB

Saved passwords. Passwords are masked unless reveal=True. Safari supports per-site lookup only — pass domain there.

set_credentialB

Write one login/password. ONLY on explicit user request.

get_site_storageB

localStorage (+sessionStorage) for one origin, e.g. "https://example.com". Values masked unless reveal=True.

set_site_storageC

Write localStorage/sessionStorage entries for an origin. ONLY on explicit user request.

sync_dataA

Copy/merge data between two browsers. Returns COUNTERS ONLY — secret values stay inside the server.

kinds defaults to all four. domain limits cookies/credentials/bookmarks by substring and is REQUIRED for per-origin storage sync (unless both browsers are quit Chromium — then whole storage dirs are raw-copied). direction=merge syncs both ways. dry_run=True (default) reports what would change without writing. Run writes only on explicit user request.

export_stateA

Export browser state to a JSON file (chmod 600). Returns path+counts. redact=True (default) masks secret values — set False for a real backup. origins lists origins whose storage to include.

import_stateA

Import a file produced by export_state. ONLY on explicit user request (dry_run=False).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct resource and action: browsers, cookies, bookmarks, credentials, site storage, sync, and export/import are all separate nouns paired with clear verbs. The read/write pairs (get_cookies/set_cookies, get_site_storage/set_site_storage) are trivially distinguishable, and sync_data's counters-only contract further separates it from the explicit per-kind getters.

Naming Consistency4/5

All names follow a consistent snake_case verb_noun pattern with a small, well-defined verb vocabulary (list/get/set/add/sync/export/import). Minor deviation: reads alternate between `list_` (list_browsers, list_bookmarks) and `get_` (get_cookies, get_credentials, get_site_storage), and writes alternate between `set_` and `add_`, though the distinctions are semantically defensible.

Tool Count5/5

At 12 tools the surface is well within the ideal 3-15 range and every tool maps to a genuine capability of the browser-data domain. No redundant or filler operations are present.

Completeness3/5

The surface covers discovery, read, write, migration, and backup/restore, but deletion is entirely absent: no remove_bookmark, delete_cookie, delete_credential, or remove_site_storage, so agents cannot undo writes. History and download data are also unaddressed, leaving notable gaps in the browse-and-manage lifecycle.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues