laravel-mcp-server

<h1 align="center">Laravel MCP Server by OP.GG</h1> <p align="center"> A powerful Laravel package to build a Model Context Protocol Server seamlessly </p> <p align="center"> <a href="https://github.com/opgginc/laravel-mcp-server/actions"><img src="https://github.com/opgginc/laravel-mcp-server/actions/workflows/tests.yml/badge.svg" alt="Build Status"></a> <a href="https://packagist.org/packages/opgginc/laravel-mcp-server"><img src="https://img.shields.io/packagist/dt/opgginc/laravel-mcp-server" alt="Total Downloads"></a> <a href="https://packagist.org/packages/opgginc/laravel-mcp-server"><img src="https://img.shields.io/packagist/v/opgginc/laravel-mcp-server" alt="Latest Stable Version"></a> <a href="https://packagist.org/packages/opgginc/laravel-mcp-server"><img src="https://img.shields.io/packagist/l/opgginc/laravel-mcp-server" alt="License"></a> </p> <p align="center"> <a href="https://op.gg/open-source/laravel-mcp-server">Official Website</a> </p> <p align="center"> <a href="README.md">English</a> | <a href="README.pt-BR.md">Português do Brasil</a> | <a href="README.ko.md">한국어</a> | <a href="README.ru.md">Русский</a> | <a href="README.zh-CN.md">简体中文</a> | <a href="README.zh-TW.md">繁體中文</a> | <a href="README.pl.md">Polski</a> | <a href="README.es.md">Español</a> </p> <p align="center"> <img src="docs/watch.gif" alt="Laravel MCP Server Demo" height="200"> </p> ## ✅ Version Information & Breaking Changes ### v1.5.0 Highlights (Oct 2025) ✅ Version 1.5.0 focuses on structured tool output, richer prompt support, and improved discoverability across the MCP protocol: - **Structured tool responses** – Use `ToolResponse::structured()` to emit plain text and JSON payloads simultaneously. Existing tools keep returning JSON strings inside the `content` array for backwards compatibility, while new stubs expose a `$autoStructuredOutput = true` flag so array responses automatically populate `structuredContent` per the MCP 2025-06-18 specification. Tool interfaces optionally expose `title()` and `outputSchema()` so schema-aware clients can display richer results. - **Tabular response helpers** – The new `FormatsTabularToolResponses` trait converts array data into CSV or Markdown tables with consistent MIME typing. Example tools and Pest tests demonstrate column normalization, validation, and multi-format output generation for data-heavy workflows. - **Enhanced tool pagination & metadata** – Cursor-based pagination for `tools/list` scales to large catalogs, configurable via the `MCP_TOOLS_PAGE_SIZE` environment variable. The server advertises schema awareness and `listChanged` hints during capability negotiation, with integration tests covering `nextCursor` behavior. - **Prompt registry & generator** – A full prompt registry backed by configuration files powers the new `prompts/list` and `prompts/get` handlers. Developers can scaffold prompts using `php artisan make:mcp-prompt`, while the service provider surfaces prompt schemas inside the MCP handshake for immediate client discovery. ### Breaking Changes in v1.1.0 (May 2025) Version 1.1.0 introduced a breaking change to the `ToolInterface`. Upgrading from v1.0.x requires refactoring every tool implementation. Refer to the [ToolInterface Migration Guide](docs/migrations/v1.1.0-tool-interface-migration.md) for automated and manual upgrade instructions. ## Overview of Laravel MCP Server Laravel MCP Server is a powerful package designed to streamline the implementation of Model Context Protocol (MCP) servers in Laravel applications. **Unlike most Laravel MCP packages that use Standard Input/Output (stdio) transport**, this package focuses on **Streamable HTTP** transport and still includes a **legacy SSE provider** for backwards compatibility, providing a secure and controlled integration method. ### Why Streamable HTTP instead of STDIO? While stdio is straightforward and widely used in MCP implementations, it has significant security implications for enterprise environments: - **Security Risk**: STDIO transport potentially exposes internal system details and API specifications - **Data Protection**: Organizations need to protect proprietary API endpoints and internal system architecture - **Control**: Streamable HTTP offers better control over the communication channel between LLM clients and your application By implementing the MCP server with Streamable HTTP transport, enterprises can: - Expose only the necessary tools and resources while keeping proprietary API details private - Maintain control over authentication and authorization processes Key benefits: - Seamless and rapid implementation of Streamable HTTP in existing Laravel projects - Support for the latest Laravel and PHP versions - Efficient server communication and real-time data processing - Enhanced security for enterprise environments ## Key Features - Real-time communication support through Streamable HTTP with SSE integration - Implementation of tools and resources