Weave Code
Symfony Profiler Mcp Laravel Package
productowner-ro/symfony-profiler-mcp
MCP server that exposes Symfony Profiler data to AI assistants, letting them query requests, performance metrics, logs, and exceptions from the web debug toolbar via the Model Context Protocol for faster debugging and analysis.
Symfony Profiler MCP exposes your Symfony Profiler data to AI assistants through the Model Context Protocol, letting tools like Claude or Cursor inspect real request telemetry instead of guessing. Query collected profiles, drill into performance, and debug issues conversationally—right from your editor.
- MCP server bridging Symfony Profiler and LLM clients
- Browse and filter captured requests and profiles
- Inspect performance metrics, timelines, and bottlenecks
- Surface exceptions, logs, and failed queries
- Drop-in integration for local Symfony development
Frequently asked questions about Symfony Profiler Mcp
- What is productowner-ro/symfony-profiler-mcp used for?
- It is a Symfony bundle that exposes Symfony Profiler data through the Model Context Protocol so AI-powered IDEs and assistants can query requests, performance metrics, logs, and debugging data. It is built on symfony/mcp-bundle. The typical use case is troubleshooting Symfony applications from an AI client instead of manually clicking through the profiler UI.
- Does symfony-profiler-mcp work with Laravel?
- The package is described as a Symfony bundle and is built on symfony/mcp-bundle, so Laravel compatibility is not claimed in the supplied overview. Laravel teams should treat it as unverified and run a timeboxed spike before committing. If you need Laravel profiler access via MCP, confirm the transport and data-source assumptions first.
- How do I install and configure symfony-profiler-mcp?
- Install it with Composer as productowner-ro/symfony-profiler-mcp at the v0.1.0 tag, then register the bundle in your Symfony kernel or bundles.php if your app does not use automatic bundle discovery. Publish any configuration the README specifies. Because the release notes payload was empty, read composer.json and the README directly for exact requirements, environment variables, and setup steps, and pin the exact patch version.
- Which Symfony and PHP versions does this MCP profiler bundle support?
- The supplied material does not list PHP or Symfony version constraints, so you must read composer.json before planning adoption. Treat any assumed support matrix as unverified at v0.1.0. Record the resolved PHP and Symfony versions in your lockfile and decision record.
- Is symfony-profiler-mcp production-ready at v0.1.0?
- No. Version 0.1.0 is an initial public release with an empty release-notes payload, no prior assessment, and no documented support window. It is evaluation-grade and should be introduced behind a feature flag in a non-production environment first. Wrap calls behind an internal adapter so a future breaking change is a one-file edit.
- What security concerns does exposing Symfony Profiler data over MCP raise?
- Profiler data can include request payloads, headers, SQL, logs, and environment details, so exposing it to an AI IDE widens the data-access surface. Restrict the MCP endpoint to trusted developers and non-production environments, and review exactly what the tools can read. No security disclosure process is documented in the supplied material, so treat that as an open risk.
- Does symfony-profiler-mcp have tests and CI?
- The supplied assessment states that test coverage and the CI matrix are unknown. Before adopting, inspect the repository test directory and CI configuration directly. If coverage is thin, budget for your own integration-test harness around the adapter.
- How does symfony-profiler-mcp integrate with AI IDEs like Claude or Cursor?
- It implements an MCP server, so MCP-capable clients can connect and issue tool calls against profiler data. The bundle sits on symfony/mcp-bundle, which supplies the MCP plumbing. You will need to configure the client with the server command and any required environment variables, but the exact setup is not documented in the supplied excerpt.
- What alternatives exist for querying Symfony Profiler data from an AI assistant?
- Alternatives include the native Symfony Profiler web UI, custom scripts that read profiler storage, or building your own MCP server over the profiler data. This package's value is that it packages that bridge on top of symfony/mcp-bundle. Compare the roughly 200 lines it may replace against the maintenance cost of a pre-1.0 dependency.
- How is symfony-profiler-mcp maintained and what is its upgrade policy for 0.x releases?
- Maintainer cadence, support window, and any 0.x upgrade policy are not documented in the supplied material. Pin to 0.1.0 exactly, because a caret range would permit 0.2.0 and semver allows breaking changes within 0.x. Set a calendar review at each Symfony major release and each 0.x minor bump, and confirm you can vendor and patch the package if needed.
Weaver
How can I help you explore Laravel packages today?