Skip to main content
Glama
duquesnay

mcp-chromium-cdp

by duquesnay

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CHROMIUM_PATHNoOverride Chromium binary path
CHROMIUM_USER_DATA_DIRNoUse custom browser profile

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
chrome_navigateB

Navigate to a specific URL in Chrome

chrome_get_current_urlA

Get the current URL of the active tab

chrome_get_titleA

Get the title of the current page

chrome_get_contentA

Get the HTML content of the current page

chrome_get_visible_textB

Get the visible text content of the current page

chrome_execute_scriptA

Execute JavaScript in the current page and return the result. ADVANCED: Use as last resort when chrome_click, chrome_type, or other structured tools cannot accomplish the task. Prefer semantic tools for better reliability.

chrome_clickA

Click on an element using a CSS selector. For React SPAs, use ensureInteractive option to trigger synthetic event handlers.

chrome_typeB

Type text into an input field using a CSS selector

chrome_screenshotA

Take a screenshot of the current page with automatic resizing to fit API limits (returns base64 encoded PNG with metadata)

chrome_open_new_tabB

Open a new tab in Chrome, optionally with a URL

chrome_close_tabA

Close the current tab

chrome_list_tabsA

List all open tabs with their titles and URLs

chrome_reloadA

Reload the current page

chrome_go_backA

Go back in browser history

chrome_go_forwardA

Go forward in browser history

chrome_check_pageA

Quick page state check without screenshot (fast health-check for autonomous agents). Returns URL, title, load state, visible errors, form count, and interactive elements count. Response time < 500ms.

chrome_extract_formsA

Extract structured form data without custom scripting. Returns fields (name, type, value, placeholder, required, label, validation rules), submit buttons, and fieldsets. Works with standard forms, React forms, and Shadow DOM forms. Identifies filled vs empty fields.

chrome_wait_forA

Wait for UI state changes after actions. Returns success status, which conditions were met, actual state, and time elapsed. On timeout, returns current state (not error) so agent can decide next action. Can chain multiple conditions.

chrome_scrollA

Scroll the page or a specific element. Supports direction (up/down/top/bottom), distance (pixels), element targeting (selector), and behavior (instant/smooth). Returns scroll position, boundary detection (atTop/atBottom), and dimensions. Useful for infinite scroll detection and pagination.

chrome_click_textA

Click an element by its visible text content (semantic alternative to chrome_click). Uses XPath contains() for text matching. Optionally filter by ARIA role. Returns actionable error with suggestions if 0 or >1 matches found. Prefer this over chrome_execute_script for clicking buttons/links.

chrome_type_textA

Type text into an input field by its associated label (semantic alternative to chrome_type). Searches for input by: label "for" attribute, parent label, aria-label, placeholder (in order). Returns actionable error with suggestions if input not found or multiple matches. Prefer this over chrome_execute_script for form filling.

chrome_extract_interactiveA

Extract all interactive elements with their text and metadata. Returns buttons, links, inputs with text, role, selector, visibility, and enabled status. Limited to 100 elements for performance. Use this to discover available interactions before calling chrome_click_text or chrome_type_text.

chrome_get_propertyA

Get a property value from an element without script injection. Uses CDP APIs for safe property access. Property name must be alphanumeric + underscore/hyphen only. Use this instead of chrome_execute_script for reading element properties.

chrome_hoverA

Hover over an element using a CSS selector. Essential for React SPAs where hover activates synthetic event handlers. Use before chrome_click when dealing with dropdowns, tooltips, or interactive elements that require hover state.

chrome_detect_spaA

Detect SPA frameworks on the page (React, Vue, Angular, Svelte). Returns framework names and versions. Use this to determine if ensureInteractive pattern is needed for clicks.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/duquesnay/mcp-chromium-cdp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server