Skip to main content
Glama
Browser-use MCP Server
by win4r

browser-use MCP Server

🔥对应视频: https://youtu.be/jsd8TpzicRQ

🔥我的微信:stoeng

A Model Context Protocol server

This is a TypeScript-based MCP server that implements a simple notes system. It demonstrates core MCP concepts by providing:

  • Resources representing text notes with URIs and metadata

  • Tools for creating new notes

  • Prompts for generating summaries of notes

Features

Resources

  • List and access notes via note:// URIs

  • Each note has a title, content and metadata

  • Plain text mime type for simple content access

Tools

  • create_note - Create new text notes

    • Takes title and content as required parameters

    • Stores note in server state

Prompts

  • summarize_notes - Generate a summary of all stored notes

    • Includes all note contents as embedded resources

    • Returns structured prompt for LLM summarization

Related MCP server: azure-devops MCP Server

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Installation

To use with Claude Desktop, add the server config:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "browser-use": {
      "command": "/path/to/browser-use/build/index.js"
    }
  }
}

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.

Available Tools

1 tool
execute_browser_taskC

执行浏览器自动化任务

Inputs: task (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'execute_browser_task' has a clearly distinct purpose that cannot be confused with any other tool in the set.

    Naming Consistency5/5

    The naming is perfectly consistent as there is only one tool, following a clear verb_noun pattern ('execute_browser_task'). No other naming conventions are present to cause inconsistency.

    Tool Count2/5

    A single tool for a browser automation server is too few for the apparent scope, as browser automation typically involves multiple operations like navigation, clicking, typing, or scraping. This feels thin and may limit functionality.

    Completeness1/5

    The tool surface is severely incomplete for browser automation, lacking essential operations such as navigating to URLs, interacting with elements, or extracting data. This will likely cause agent failures in handling common browser tasks.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers