Skip to main content
Glama
seabassgonzalez

MCP Browser Screenshot Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HEADLESSNoControls whether the browser runs in headless modetrue

Instructions

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

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
browser_launchC

Launch a new browser instance

browser_navigateC

Navigate to a URL

browser_closeA

Close the browser instance

screenshot_captureC

Take a screenshot of the current page

screenshot_viewportC

Take a screenshot with specific viewport settings

browser_execute_scriptC

Execute JavaScript in the browser context

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. The browser_* tools manage browser lifecycle and navigation, while the screenshot_* tools handle different screenshot capture scenarios, making misselection unlikely.

Naming Consistency5/5

Perfectly consistent verb_noun pattern throughout. All tools follow the same naming convention with clear prefixes (browser_ and screenshot_) and descriptive action-object combinations.

Tool Count5/5

Six tools is well-scoped for a browser screenshot server. Each tool earns its place by covering essential browser control and screenshot functionality without redundancy.

Completeness4/5

The toolset covers the core browser automation and screenshot workflow comprehensively. Minor gaps might include page interaction tools (like clicking elements) or additional screenshot options, but the basic lifecycle is complete.

Maintenance

ActivityInactive
ResponsivenessNo issues