<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/laravel-mcp-1-0-is-released-qlrfaoxe5" -->

---
title: Laravel MCP 1.0 Is Released | daily.dev
description: Laravel MCP 1.0 is the first stable release of Laravel's package for building Model Context Protocol servers, adding support for protocol revision 2026-07-28....
canonical: https://daily.dev/posts/laravel-mcp-1-0-is-released-qlrfaoxe5
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Laravel MCP 1.0 Is Released | daily.dev
og:description: Laravel MCP 1.0 is the first stable release of Laravel's package for building Model Context Protocol servers, adding support for protocol revision 2026-07-28....
og:url: https://daily.dev/posts/laravel-mcp-1-0-is-released-qlrfaoxe5
og:image: https://api.daily.dev/og/posts/qlrFAoXE5.png
og:image:alt: Laravel MCP 1.0 Is Released
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Laravel MCP 1.0 Is Released

**[Laravel News](https://daily.dev/sources/ln)** · [@ericlbarnes](https://daily.dev/ericlbarnes) · 4 min read · 0 upvotes · 0 comments

## Summary

Laravel MCP 1.0 is the first stable release of Laravel's package for building Model Context Protocol servers, adding support for protocol revision 2026-07-28. New capabilities include searchable tool catalogs to keep large tool lists out of the model's context window, cache hints for controlling client-side caching, stateless request handling that removes session tracking, and OAuth changes requiring PKCE support plus Client ID Metadata Documents. Older clients using the initialize handshake continue to work. Upgrading from 0.9 requires new headers on requests and updated test setups, detailed in the 1.0 upgrade guide.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://laravel-news.com/laravel-mcp-1-0>

## Questions this post answers

### What breaking changes come with upgrading Laravel MCP from 0.9 to 1.0?

Upgrading from 0.9 to 1.0 removes session tracking, requiring migration to the new stateless protocol. The MCP-Session-Id header, Request::sessionId(), Request::setSessionId(), and the SessionInitialized event are all removed. POST requests using the new protocol need matching MCP-Protocol-Version and Mcp-Method headers, and calls like tools/call also require an Mcp-Name header; mismatches return HTTP 400 with JSON-RPC error -32020.

_Track Laravel MCP upgrade guides like this one on daily.dev before migrating existing servers._

### How does Laravel MCP's ToolSearch reduce context window usage for AI agents?

ToolSearch lets developers keep frequently used tools always visible to the agent while placing less common tools behind a searchable index, so the full tool catalog doesn't consume context window space upfront. The package registers a search_tools tool that returns matching tools by name, description, and inputs, and an execute_tools tool that runs them by name, letting agents discover tools only when needed.

_Developers optimizing agent context budgets can follow tooling patterns like this via daily.dev._

### What OAuth requirement changed in Laravel MCP 1.0 for authorization servers?

Laravel MCP 1.0 requires PKCE support from authorization servers; OAuthClient::redirect() now throws an OAuthException if the server's metadata omits code_challenge_methods_supported entirely, whereas previously it only rejected servers that listed the field without S256 support. The release also adds Client ID Metadata Documents as an alternative to Dynamic Client Registration, which is deprecated under MCP 2026-07-28.

_Anyone hardening OAuth flows for MCP servers can keep up with changes like this through daily.dev._

## Similar posts on daily.dev

- [Laravel MCP: A Complete Guide](https://daily.dev/posts/laravel-mcp-a-complete-guide-zxqn7ceg1) · Laravel · 6 upvotes · 0 comments
- [Release v1.0 of the official MCP C\# SDK](https://daily.dev/posts/release-v1-0-of-the-official-mcp-c-sdk-y53o7hb5x) · ASP.NET Blog · 19 upvotes · 1 comments
- [Laravel Boost Update Adds Support for the New MCP Protocol](https://daily.dev/posts/laravel-boost-update-adds-support-for-the-new-mcp-protocol-8827svtqm) · Laravel News · 3 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#php](https://daily.dev/tags/php), [#laravel](https://daily.dev/tags/laravel), [#mcp](https://daily.dev/tags/mcp), [#oauth](https://daily.dev/tags/oauth)

[View this post on daily.dev](https://daily.dev/posts/laravel-mcp-1-0-is-released-qlrfaoxe5)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Laravel MCP 1.0 Is Released","url":"https://daily.dev/posts/laravel-mcp-1-0-is-released-qlrfaoxe5","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/laravel-mcp-1-0-is-released-qlrfaoxe5"},"datePublished":"2026-09-15T14:51:43.820Z","dateModified":"2026-09-16T16:00:15.655Z","description":"Laravel MCP 1.0 is the first stable release of Laravel's package for building Model Context Protocol servers, adding support for protocol revision 2026-07-28....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ece64d3779f46116c56e04707c4f1ad2?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ece64d3779f46116c56e04707c4f1ad2?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Laravel News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Person","name":"Eric L. Barnes","url":"https://daily.dev/ericlbarnes","image":"https://media.daily.dev/image/upload/s--K6f982B3--/f_auto/v1755288662/avatars/avatar_9SjPngRVLKMb8ob1eVrqZ?_a=BAMClqZW0","description":"Founder of Laravel News","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":2460}},"commentCount":0,"discussionUrl":"https://daily.dev/posts/laravel-mcp-1-0-is-released-qlrfaoxe5","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,php,laravel,mcp,oauth","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Laravel News","item":"https://daily.dev/sources/ln"},{"@type":"ListItem","position":3,"name":"Laravel MCP 1.0 Is Released"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/laravel-mcp-1-0-is-released-qlrfaoxe5#faq","mainEntity":[{"@type":"Question","name":"What breaking changes come with upgrading Laravel MCP from 0.9 to 1.0?","acceptedAnswer":{"@type":"Answer","text":"Upgrading from 0.9 to 1.0 removes session tracking, requiring migration to the new stateless protocol. The MCP-Session-Id header, Request::sessionId(), Request::setSessionId(), and the SessionInitialized event are all removed. POST requests using the new protocol need matching MCP-Protocol-Version and Mcp-Method headers, and calls like tools/call also require an Mcp-Name header; mismatches return HTTP 400 with JSON-RPC error -32020. Track Laravel MCP upgrade guides like this one on daily.dev before migrating existing servers."}},{"@type":"Question","name":"How does Laravel MCP's ToolSearch reduce context window usage for AI agents?","acceptedAnswer":{"@type":"Answer","text":"ToolSearch lets developers keep frequently used tools always visible to the agent while placing less common tools behind a searchable index, so the full tool catalog doesn't consume context window space upfront. The package registers a search_tools tool that returns matching tools by name, description, and inputs, and an execute_tools tool that runs them by name, letting agents discover tools only when needed. Developers optimizing agent context budgets can follow tooling patterns like this via daily.dev."}},{"@type":"Question","name":"What OAuth requirement changed in Laravel MCP 1.0 for authorization servers?","acceptedAnswer":{"@type":"Answer","text":"Laravel MCP 1.0 requires PKCE support from authorization servers; OAuthClient::redirect() now throws an OAuthException if the server's metadata omits code_challenge_methods_supported entirely, whereas previously it only rejected servers that listed the field without S256 support. The release also adds Client ID Metadata Documents as an alternative to Dynamic Client Registration, which is deprecated under MCP 2026-07-28. Anyone hardening OAuth flows for MCP servers can keep up with changes like this through daily.dev."}}]}
```