Overview
What is Laravel Telescope MCP?
Laravel Telescope MCP is an extension for Laravel Telescope that exposes telemetry data via the Model Context Protocol (MCP) to AI assistants such as Cursor, Claude, and Copilot Chat. Designed for developers using Telescope to inspect application metrics, it translates natural-language queries into MCP operations and returns precise insights.
How to use Laravel Telescope MCP?
Ensure Laravel Telescope is installed, then add the package via Composer (composer require lucianotonet/laravel-telescope-mcp) and optionally publish the configuration. Set TELESCOPE_MCP_ENABLED=true and a path (default telescope-mcp) in your .env. Connect an AI client by adding an MCP server configuration pointing to the HTTP endpoint, using npx mcp-remote as a bridge (e.g., http://localhost:8000/telescope-mcp). The AI can then query Telescope data using natural language.
Key features of Laravel Telescope MCP
- Exposes 18 Telescope data types as MCP tools (batches, cache, commands, dumps, events, exceptions, gates, HTTP client, jobs, logs, mail, models, notifications, queries, Redis, requests, schedule, views)
- Prune tool to remove old Telescope entries
- Translates natural-language queries into MCP operations
- Configurable endpoint path, middleware, timeouts, and logging
- Works with HTTP or HTTPS transports
- Supports authentication via Laravel middleware
Use cases of Laravel Telescope MCP
- Quickly fetch the last 5 error logs using a simple AI prompt
- Identify SQL queries longer than 100ms in the past twenty minutes
- Show all last failed queue jobs
- Summarize HTTP requests with status codes ≥500 since the last hour
FAQ from Laravel Telescope MCP
Do I need Laravel Telescope installed first?
Yes, Laravel Telescope must be properly installed and configured in your application before adding this package.
What runtime dependencies are required?
A Laravel application with PHP and Composer, plus Node.js/npx (for the MCP remote proxy used by clients like Cursor).
How does the MCP endpoint communicate?
Via HTTP (or HTTPS). The package exposes a manifest and tools at a configurable path (default telescope-mcp). AI clients connect using the mcp-remote transport.
How can I secure the endpoint?
Use Laravel middleware such as auth:sanctum or auth.basic to protect the route, as configured in config/telescope-mcp.php.
Can I customize the endpoint path or other settings?
Yes, publish the configuration and modify TELESCOPE_MCP_PATH, middleware stacks, request timeouts, payload limits, and logging behavior.
