Laravel MCP

Created By
mohamedahmed01a year ago
Laravel Based Implementation for Model Context Protocol
Overview

What is Laravel MCP?

Laravel MCP is a Laravel package designed for implementing the Model Context Protocol (MCP) in Laravel applications, facilitating communication between AI models and Laravel applications through standardized interfaces.

How to use Laravel MCP?

To use Laravel MCP, install it via Composer, configure the server settings, and start the server using the provided Artisan commands. You can then register tools and manage resources through the MCP server.

Key features of Laravel MCP?

  • Multiple transport options (HTTP, WebSocket, Stdio)
  • Server capabilities for tool registration, resource management, and logging
  • Dynamic prompt handling and progress tracking
  • Comprehensive logging system with multiple log levels

Use cases of Laravel MCP?

  1. Building AI-driven applications that require real-time communication.
  2. Implementing custom tools for data processing and analysis.
  3. Managing resources and prompts for AI model interactions.

FAQ from Laravel MCP?

  • What are the system requirements for Laravel MCP?

PHP 8.1 or higher, Laravel 10.x, and several PHP extensions are required.

  • How do I install Laravel MCP?

Install via Composer with the command: composer require laravelmcp/mcp.

  • Can I use Laravel MCP for non-Laravel applications?

Laravel MCP is specifically designed for Laravel applications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mohamedahmed01
Star
1
Language
PHP
License
MIT license

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 hours ago