Magento 2 Debug Bar FAQs

Question 1

Does this tool capture AJAX, REST, and GraphQL requests?

Accepted Answer

Yes. Because every request writes a bounded JSON profile to disk rather than directly modifying the HTTP response body, the bar can capture and display diagnostics for asynchronous AJAX, GraphQL, and REST API calls.

Question 2

Is Magento 2 Debug Bar compatible with Hyvä and Luma themes?

Accepted Answer

Yes. The debug bar renders in an isolated shadow DOM using its own bundled Alpine.js, ensuring seamless compatibility across Hyvä Themes, standard Luma storefronts, backend admin panels, and headless architectures without introducing frontend asset conflicts or CSP violations.

Question 3

How does the built-in MCP server benefit AI agents?

Accepted Answer

The module includes read-only MCP tools over stdio (such as list_debug_profiles, inspect_debug_queries, and get_debug_findings), allowing AI coding assistants like Claude to directly inspect exact execution profiles, detect bottlenecks, and analyze errors instead of relying on guessing or screenshots.

Question 4

What security controls prevent sensitive data leakage?

Accepted Answer

The tool automatically disables itself outside developer mode unless configured with a 32+ character key, strips query keys into secure HttpOnly cookies, redacts sensitive PII and SQL literals at record time, marks debug responses as no-store, and restricts profiles with strict 0600 file permissions.

Question 5

What is Magento 2 Debug Bar?

Accepted Answer

Magento 2 Debug Bar is a developer profiling tool that captures request performance, database queries, cache diagnostics, and client-side states into structured profiles, viewable via an in-browser shadow root interface or read-only Model Context Protocol (MCP) server for AI coding agents.

Magento 2 Debug Bar

Key Features

Use Cases

Neon

Figma Context

Magic

Meme Maker

Agent Skill Creator

OpenClaw Channel Configurator