Skip to main content
Glama

How to View console.log Output in Chrome MCP tools

Production-ready MCP servers that extend AI capabilities through file access, database connections, APIs, and contextual services.

71,336 tools. Last updated 2026-02-12 19:24
  • Start capturing browser console logs (console.log, console.error, console.warn) to monitor JavaScript output and debug web applications during automated browser sessions.
    MIT
  • Focus a specific Chrome tab by its unique ID, bringing it to the front for active use. Requires the tab ID from get_tabs output, enabling precise tab control in the MCP Browser Tabs Server.
    MIT
  • Close a specific Chrome tab by its unique ID, unaffected by tab reordering, window changes, or index shifting. Use the tab ID from the get_tabs output for precise control.
    MIT
  • Establish a debugging session by connecting to Chrome DevTools Protocol endpoints for Node.js, Chrome, or Edge to enable breakpoints, code stepping, and variable inspection.
    Apache 2.0
  • Verify CSS or JavaScript feature compatibility in Chrome 37 to identify browser support issues and ensure cross-browser functionality.
    MIT

Interested in MCP?

Join the MCP community for support and updates.

RedditDiscord

Matching MCP servers