Skip to main content
Glama

browser-use MCP server

A MCP server project

Components

Resources

The server implements a simple note storage system with:

  • Custom note:// URI scheme for accessing individual notes

  • Each note resource has a name, description and text/plain mimetype

Prompts

The server provides a single prompt:

  • summarize-notes: Creates summaries of all stored notes

    • Optional "style" argument to control detail level (brief/detailed)

    • Generates prompt combining all current notes with style preference

Tools

The server implements one tool:

  • add-note: Adds a new note to the server

    • Takes "name" and "content" as required string arguments

    • Updates server state and notifies clients of resource changes

Related MCP server: Datetime MCP Server

Configuration

[TODO: Add configuration details specific to your implementation]

Quickstart

Install

Claude Desktop

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

Development

Building and Publishing

To prepare the package for distribution:

  1. Sync dependencies and update lockfile:

uv sync
  1. Build package distributions:

uv build

This will create source and wheel distributions in the dist/ directory.

  1. Publish to PyPI:

uv publish

Note: You'll need to set PyPI credentials via environment variables or command flags:

  • Token: --token or UV_PUBLISH_TOKEN

  • Or username/password: --username/UV_PUBLISH_USERNAME and --password/UV_PUBLISH_PASSWORD

Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.

You can launch the MCP Inspector via npm with this command:

npx @modelcontextprotocol/inspector uv --directory /Users/adamholsinger/mcp-servers/browser-use run browser-use

Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

Available Tools

1 tool
add-noteC

Add a new note

Inputs: name (required), content (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    C2.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or confusion between tools. The tool 'add-note' has a clear and distinct purpose that cannot be misselected against other tools.

    Naming Consistency5/5

    Since there is only one tool, it inherently follows a consistent naming pattern. The tool name 'add-note' uses a verb_noun format, which is clear and predictable, and there are no other tools to cause inconsistency.

    Tool Count2/5

    A single tool is too few for a server named 'browser-use', which suggests a broader scope related to browser interactions. This minimal set feels thin and incomplete for the implied domain, limiting functionality.

    Completeness1/5

    The tool set is severely incomplete for a browser-use server. With only an 'add-note' tool, there are obvious gaps in core browser operations like navigation, clicking, or form filling, making it inadequate for typical browser automation tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers