MCP SDK for Laravel

Created By
ronydebnatha year ago
WIP - Model Context Protocol (MCP) SDK for Laravel. A robust, extensible Laravel package that implements the Model Context Protocol (MCP) for building AI-driven conversational applications.
Overview

What is MCP SDK for Laravel?

MCP SDK for Laravel is a robust and extensible Laravel package that implements the Model Context Protocol (MCP) for building AI-driven conversational applications.

How to use MCP SDK for Laravel?

To use the MCP SDK, install the package via composer and publish the configuration file. You can then use the MCP client or server functionalities in your Laravel application.

Key features of MCP SDK for Laravel?

  • Easy installation and configuration via composer.
  • Supports both client and server functionalities for MCP.
  • Built-in authentication and memory management.
  • Streaming capabilities for real-time communication.

Use cases of MCP SDK for Laravel?

  1. Building chatbots and conversational agents.
  2. Implementing AI-driven customer support systems.
  3. Creating interactive applications that require context management.

FAQ from MCP SDK for Laravel?

  • Is MCP SDK suitable for all Laravel applications?

Yes! It is designed to integrate seamlessly with any Laravel application.

  • How do I handle multiple messages?

You can use the sendMultiple method to handle multiple messages at once.

  • What is the licensing for MCP SDK?

The MCP SDK is licensed under the MIT License.

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

Recommend Servers

View All
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.

21 hours ago