Skip to content
Tool

browser_upload_file

2 published MCP servers declare browser_upload_file. poltertab and chromium-bridge have the highest trust scores right now. Servers describe it as: selector (required), paths (required), method ("picker" or "drop"), tabId, session Few published servers use this exact name, so read each listing before you install. Open a server for its install config and the rest of its tools.

2 serversUncommon name
Trust score 38 of 100, Limited

poltertab

by abhinav162 · JavaScript

Drive and scrape your existing Chrome profile from any AI assistant — no headless browser.

Registry
LicenseQualityMaintenanceLicense: A. ISC is a permissive open source license.Quality: B. 74/100 for listing completeness. Lost points: 23 of 28 tools barely described, short summary, no docs link.Maintenance: A. Last commit or release 12 days ago.
1 stars—/wk weekly downloads28 tools
Trust score 13 of 100, Limited

MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation

Registry
LicenseQualityMaintenanceLicense: Not graded. No license is recorded for this server.Quality: A. 89/100 for listing completeness. Lost points: 1 of 14 tools barely described, short summary, no docs link.Maintenance: Not graded. No commit or release date has been recorded.
— stars—/wk weekly downloads14 tools

FAQ

What is the browser_upload_file MCP tool?
browser_upload_file is a tool name MCP servers declare. A description they publish is: selector (required), paths (required), method ("picker" or "drop"), tabId, session
Which MCP servers provide browser_upload_file?
2 published servers declare browser_upload_file. Highest in the current trust order: poltertab and chromium-bridge.
How do I use browser_upload_file?
Install a server that declares browser_upload_file, then call it from Claude, Cursor, or VS Code. Each server page has the config for that client and the other tools that server exposes.