mcpField
L
Laravel MCP (Model Context Protocol)

Laravel MCP (Model Context Protocol)

Local
github.com/InnoGEDeveloper Tools17Updated 8w ago

About Laravel MCP (Model Context Protocol)

Laravel MCP is an unmaintained proof-of-concept package for building MCP servers in Laravel. It supports STDIO transport and provides resource providers and customizable tools; the project recommends using the official laravel/mcp package instead.

Key features

  1. 01Build MCP servers in Laravel
  2. 02Expose Eloquent and in-memory resources
  3. 03Define custom tools
  4. 04STDIO transport

Use cases

  1. 01Prototype MCP support in a Laravel application
  2. 02Expose application data through resource providers
  3. 03Define actions for an MCP client

MCP support

The package implements MCP servers over STDIO, exposing configured resources and tools to MCP clients. It is no longer maintained and has been replaced by the official laravel/mcp package.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"laravel": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/inspector"
]
}
}
}
Run commandnpx -y @modelcontextprotocol/inspector

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@modelcontextprotocol/inspector

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Laravel MCP (Model Context Protocol)

Warning

This package is no longer maintained.

It was a proof of concept and is not developed further. It is now 100% replaced by the official laravel/mcp package. Please use that instead.

Latest Version on Packagist GitHub Tests Action Status GitHub Code Style Action Status Total Downloads

A Laravel package that implements the Model Context Protocol (MCP), enabling seamless communication between your Laravel application and AI assistants or other systems through a standardized API. Please note that this package is still in development and not yet ready for production use.

Installation

You can install the package via composer:

composer require innoge/laravel-mcp

Basic Usage

Setting Up an MCP Server

This package currently only supports creating MCP servers via the STDIO transport. HTTP transport is not supported yet but will be added in the future.

Create a command to serve your MCP server:

<?php

namespace App\Console\Commands;

use Illuminate\Console\Command;
use InnoGE\LaravelMcp\Commands\ServesMcpServer;

class McpServerCommand extends Command
{
    use ServesMcpServer;

    protected $signature = 'mcp:serve';
    protected $description = 'Start an MCP server';

    public function handle(): int
    {
        return $this->serveMcp('your-app-name', '1.0.0');
    }

    private function getTools(): array
    {
        return [
            // List your tool classes here
        ];
    }

    private function getResources(): array
    {
        return [
            // List your resource providers here
        ];
    }
}
Resources

Resources allow you to expose your application's data models through the MCP protocol. The package provides two types of resource providers:

  1. EloquentResourceProvider: Expose Eloquent models
use InnoGE\LaravelMcp\Resources\EloquentResourceProvider;
use App\Models\User;

// In your getResources() method:
return [
    new EloquentResourceProvider(User::query(), 'users', 'A User of the Application')
];
  1. InMemoryResourceProvider: Expose custom data structures or non-Eloquent data
use InnoGE\LaravelMcp\Resources\InMemoryResourceProvider;
use InnoGE\LaravelMcp\Types\Resources\ResourceContent;
use InnoGE\LaravelMcp\Types\Resources\ResourceItem;

// Create a resource provider
$resourceProvider = new InMemoryResourceProvider();

// Add example documents as resources
$resourceProvider->addResource(
    new ResourceItem('doc://example/document1', 'Example Document 1', 'This is an example document', 'text/plain', 1024),
    new ResourceContent('doc://example/document1', 'text/plain', 'This is the content of the document')
);

$resourceProvider->addResource(
    new ResourceItem('doc://example/document2', 'Example Document 2', 'This is an example document 2', 'text/plain', 1024),
    new ResourceContent('doc://example/document2', 'text/plain', 'This is the content of the document 2')
);

// In your getResources() method:
return [
    $resourceProvider
];
Tools

Tools define actions that can be performed through the MCP protocol:

  • Built-in Example Tools:

    • HelloTool: A simple hello world example
    • ClockTool: Returns the current time
  • Custom Tools: Create your own by implementing the ToolInterface

use InnoGE\LaravelMcp\Tools\Examples\HelloTool;
use InnoGE\LaravelMcp\Tools\Examples\ClockTool;
use App\MCP\Tools\YourCustomTool;

// In your getTools() method:
return [
    HelloTool::class,
    ClockTool::class,
    YourCustomTool::class,
];
Creating a Tool

Tools are the core functionality of MCP, allowing AI assistants to interact with your Laravel application. They provide a way to execute specific actions in your application through a well-defined interface.

Real-world examples of MCP tools include:

  • Database Operations: Create, read, update, or delete records
  • External API Integration: Make API calls to third-party services
  • File Management: Upload, download, or process files
  • Authentication: Verify user credentials or generate tokens
  • Reporting: Generate reports or export data
  • Email/Notification: Send messages to users

Example Tool:

<?php

namespace App\MCP\Tools;

use Illuminate\Support\Facades\Artisan;
use InnoGE\LaravelMcp\Tools\Tool;
use Symfony\Component\Console\Output\BufferedOutput;

class CallArtisanCommandTool implements Tool
{
    /**
     * Get the tool name
     */
    public function getName(): string
    {
        return 'call-artisan-command';
    }

    /**
     * Get the tool description
     */
    public function getDescription(): string
    {
        return 'Call a Laravel Artisan command';
    }

    /**
     * Get the input schema for the tool
     */
    public function getInputSchema(): array
    {
        return [
            'type' => 'object',
            'properties' => [
                'command' => [
                    'type' => 'string',
                    'description' => 'The Artisan command to call (e.g. "migrate")',
                ],
            ],
            'required' => ['command'],
        ];
    }

    /**
     * Execute the tool with the provided arguments
     */
    public function execute(array $arguments): string
    {
        $command = $arguments['command'];

        $outputBuffer = new BufferedOutput;

        Artisan::call($command, [], $outputBuffer);

        return $outputBuffer->fetch();
    }
}

Testing your MCP Server

Use Modelcontext Protocol Inspector to test the MCP server:

npx @modelcontextprotocol/inspector php /path/to/your/app/artisan mcp:serve

Adding your MCP Server to Claude Desktop

Edit your Claude Desktop config file:

~/Library/Application Support/Claude/claude_desktop_config.json

Add your MCP server to the config file:

{
  "mcpServers": {
    "laravel-mcp": {
      "command": "php",
      "args": [
        "/path/to/your/app/artisan",
        "mcp:serve"
      ]
    }
  }
}

Now you can use your MCP server in Claude Desktop. Please note that Claude currently does not use MCP resources. If you want to access data of your application you can use tool calls.

Testing

composer test

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

License

The MIT License (MIT). Please see License File for more information.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.