- Is killerwolf/mcp-profiler-bundle a Laravel package?
- No. It is a Symfony bundle that registers into Symfony's DI compilation pipeline, listens on kernel events, and reads from the Web Profiler's FileProfilerStorage. There is no Laravel ServiceProvider, no publishable config, and no facade, so composer require will not give a Laravel app anything useful. The reusable part is the MCP tool schema design, not the artifact.
- Does this bundle work with Laravel Telescope, Pulse, or Debugbar?
- No. It is built specifically against the Symfony Web Profiler and has no adapter for Laravel's observability stack. A Laravel team would need to reimplement the same idea over Telescope's entries table, which is a few days of work, not a config change. The Symfony-specific adapter layer is the part that does not port.
- Is killerwolf/mcp-profiler-bundle still maintained?
- No. Release 0.2.1 is explicitly titled "Final release: this bundle is deprecated," and no further updates are planned. The README points users at Symfony AI Mate, and the only remaining changes were a PHP 8.4 nullable-type fix and CI housekeeping. A deprecated package also receives no security patches.
- What should I use instead of this MCP profiler bundle?
- Symfony's documented successor is Symfony AI Mate: symfony/ai-mate plus symfony/ai-symfony-mate-extension and symfony/ai-monolog-mate-extension. You initialise it with vendor/bin/mate init and populate capabilities via vendor/bin/mate discover. It uses an extension-based architecture where Mate is the host and extensions contribute capabilities.
- How do I install and enable it in a Symfony app?
- Install with composer require killerwolf/mcp-profiler-bundle, enable the bundle in config/bundles.php, and make sure the profiler is active in your dev environment. Only do this if you consciously accept that the package is deprecated and unsupported. For new work, stand up Symfony AI Mate instead.
- How do I remove killerwolf/mcp-profiler-bundle from an existing Symfony project?
- Run composer remove killerwolf/mcp-profiler-bundle, delete its line from config/bundles.php, and remove the mcp:server:run entry from your MCP client configuration. Then install Symfony AI Mate and run vendor/bin/mate init followed by vendor/bin/mate discover. The 0.2.1 release notes give this as the intended migration path.
- Is it safe to expose profiler data through an MCP server to an AI agent?
- Profiler data is not innocuous: it can include request bodies, headers with bearer tokens and cookies, session payloads, and SQL with bound parameters, all of which can flow into a third-party model provider's context. That is acceptable only in a dev-only, single-developer environment, never in shared staging, preview, or CI with real credentials. Because the bundle is deprecated, header-redaction or transport-auth weaknesses will not be fixed.
- Which Symfony and PHP versions does version 0.2.1 support?
- The last release included a PHP 8.4 nullable-type fix, so it is expected to run on modern PHP, but you should read the composer.json constraints in the 0.2.1 tag before relying on it. Since no further releases are planned, compatibility with future Symfony versions is not guaranteed. Check this before adding it to any long-lived project.
- Can I build the same MCP profiling panel for a Laravel application?
- Yes, and that is the sensible path for a Laravel shop. The valuable idea is how request, query, and timing data is shaped into JSON-RPC tool responses an agent can consume without blowing its context window, and that design is framework-agnostic. Reimplement it over Laravel Telescope's entries table rather than trying to port the Symfony bundle.
- What does the Profiler panel actually show for MCP requests?
- It adds a dedicated panel per MCP request that lists the registered tools, resources, and prompts your server exposes. It also traces tool invocations with their arguments, results, and timing, so you can debug integrations and spot slow calls without digging through logs. That is useful information, but it does not change the fact that the bundle itself is Symfony-only and deprecated.