mcp-browser-dev-tools
Browser MCP server for AI agents: batch actions, waits, and checks into one call on Chrome, Edge, or Firefox (CDP and WebDriver BiDi)
No outside reports on file
mcp-browser-dev-tools fetches arbitrary web URLs; restrict its folder reach, network access, and credentials before installing.
Based on public adoption and transparency signals as of Oct 19, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesNo local folder access notedLOW
- Command executionNo shell command runner notedLOW
- Network reachFetches arbitrary web URLsREVIEW
- CredentialsNo API token requiredLOW
- Package sourcenpm (mcp-browser-dev-tools)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
npx -y mcp-browser-dev-toolsAbout MCP Browser Dev Tools
MCP Browser Dev Tools is an MCP server focused on Web & browsing and Files & documents: Browser MCP server for AI agents: batch actions, waits, and checks into one call on Chrome, Edge, or Firefox (CDP and WebDriver BiDi).
It is published on npm as mcp-browser-dev-tools and hosted on GitHub at hinaser/mcp-browser-dev-tools (1 GitHub stars, 135 weekly npm downloads, last repository push on 2026-10-21). Based on its public metadata, its operational scope includes: fetches arbitrary web urls.
Setup
These use the package this listing points to. Check the project’s own instructions before running anything.
npm command
npx -y mcp-browser-dev-toolsMCP client config
For Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json).
{
"mcpServers": {
"mcp-browser-dev-tools": {
"command": "npx",
"args": [
"-y",
"mcp-browser-dev-tools"
]
}
}
}Why this grade
Signal-based grade (1/7 points): public source code. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- GitHub stars
- 1
- Weekly npm downloads
- 135
- Listing last refreshed
- 2026-10-28
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Security reports
No reports found for this package in our research (last checked 2026-10-29).
Risks to watch for
- Untrusted web content & prompt injection: Fetches arbitrary web pages or remote endpoints where hidden instructions could manipulate agent behavior. Restrict outbound domains and review tool outputs.
- Dependency & version pinning: Distributed via npm (mcp-browser-dev-tools). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.
How to lower the risk
Least-privilege permissions
- Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
- Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.
Network isolation
- Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
- If your IT team can, limit which websites and services it is allowed to contact.
Monitoring
- Check its activity history or logs weekly at first, and look at what it changed or sent.
- Turn on alerts for new logins or unusual usage on any account it connects to.
Red flags to watch for
- It asks for more access than its job requires, or prompts you to paste passwords.
- It suddenly updates with new owners, or starts contacting unfamiliar websites.
Questions
How do I install MCP Browser Dev Tools?
Run npx -y mcp-browser-dev-tools in your terminal, or add the server entry to your claude_desktop_config.json or .cursor/mcp.json as shown in the Setup section on this page. Full setup docs and environment variables are in github.com/hinaser/mcp-browser-dev-tools.
Are there security reports about MCP Browser Dev Tools?
No reports found for this package in our research (last checked 2026-10-29). MCP Browser Dev Tools currently holds Grade D (High risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.
Is MCP Browser Dev Tools actively maintained?
MCP Browser Dev Tools has 1 GitHub stars and 135 weekly npm downloads, with its latest repository commit pushed on 2026-10-21. Our directory data was last refreshed on 2026-10-28. Check recent commit activity, release tags, and open issues at github.com/hinaser/mcp-browser-dev-tools before pinning it in production.
What are alternatives to MCP Browser Dev Tools?
You can compare MCP Browser Dev Tools side by side with other Browser MCP servers in the Related tools section on this page, or use the Compare tool on AgentArmorHQ.
Key facts
- Type
- App connector
- Publisher
- hinaser
- Source code
- github.com/hinaser/mcp-browser-dev-tools
- Install command
- npm install mcp-browser-dev-tools
- Est. context load
- ~850 tokens / turn (~5 tool schemas, 0.43% of 200k context)
- Popularity
- 1 GitHub stars, 135 weekly npm downloads
- Last updated
- 2026-10-28
- Last graded
- 2026-10-20
Community
Discussions for MCP Browser Dev Tools
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude