Search Results for "console"

chrome-devtools-mcp is an MCP server that connects AI agents to the Chrome DevTools Protocol so they can inspect pages, record traces, read console/network data, and modify the live browser state under user control. It makes a running Chrome instance visible to MCP clients, enabling agents to debug websites end-to-end—launching Chrome, navigating, profiling, and collecting artifacts in a structured way. The repository spells out environment requirements and cautions that exposing a live browser to agents grants powerful access, so sensitive data should be handled carefully. ...

An AI-driven Mini Kubernetes Dashboard designed to simplify cluster management, offering a lightweight console tool with integrated large language model capabilities for enhanced operational efficiency. ​

...It works together with a companion browser extension: when a user reproduces a bug or a complicated UI interaction, the extension captures a rich session log, including screen/video recording, network traffic, console logs, DOM events, storage changes, and more, and exports it. The MCP server then loads this captured “flow” and exposes it to the AI agent via the Model Context Protocol (MCP), letting the agent examine, search, filter, and reason about the session just as a human developer would, without needing the agent to re-run the flow or rely on minimal reproduction data (logs, screenshots).

web-eval-agent is a Model Context Protocol (MCP) server that spins up a browser-use–capable debugging agent to autonomously run and evaluate web apps straight from your editor. It’s positioned as a “let the coding agent debug itself” companion: the agent launches the app, navigates flows, captures evidence, and iterates on failures without manual copy-pasting of logs. The repository focuses on developer ergonomics, exposing typed MCP tools so clients like Claude Desktop can start sessions,...

Browser MCP is an MCP server plus browser integration that lets AI apps automate the user’s real browser instead of launching a separate automation session. By adapting a Playwright-style approach to control the running browser profile, it reuses logged-in sessions and cookies, which reduces re-authentication friction and helps avoid some bot-detection heuristics. The server exposes structured tools for navigation, element interaction, and artifact capture (DOM, screenshots, logs), all...