[Add] Resource Template Implementation

[keshav-k3]

Issue

• Support resource templates #69

Description

Resource Templates Implementation

Adds support for Resource Templates in the MCP server, enabling dynamic resources with URI patterns.

Changes

• Core: New ResourceTemplate class extending Primitive with uriTemplate and mimeType support
• Pattern Matching: UriTemplateMatcher utility for RFC 6570 URI template matching and variable extraction
• Dynamic Reading: ReadResource enhanced to match URI patterns and inject extracted variables into template handlers
• Method Handler: ListResourceTemplates for resources/templates/list endpoint
• Generator: make:mcp-resource-template artisan command with stub file
• Integration: Updated Server and ServerContext to support resource templates
• Tests: Complete unit test coverage for new functionality

Usage
php artisan make:mcp-resource-template UserProfile

Generates a resource template with dynamic URI patterns like file://resources/user-profile/{id}

[github-actions]

Thanks for submitting a PR!

Note that draft PR's are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.

[alejojperez]

@keshav-k3 Hey, thank you for your contribution. I'm testing the code in your branch, and there is a small bug at \Laravel\Mcp\Server\Methods\ReadResource::55. You are binding the request to the container, but the arguments get overridden because of the logic that exists on \Laravel\Mcp\Server\McpServiceProvider::72. To make the path variables available on the request, you should change the implementation to something like this:

Container::getInstance()->afterResolving(Request::class, function (Request $mcpRequest) use ($variables): void {
    foreach ($variables as $key => $value) {
        $mcpRequest->merge([$key => $value]);
    }
});

CC: @taylorotwell

[keshav-k3]

@alejojperez Hey, appreciate the spot! I’ve fixed it and tested the change — LGTM！

[alejojperez]

Thanks for submitting a PR!

Note that draft PR's are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.

@keshav-k3 Hey, remember to mark your PR as ready for review! 😊

[taylorotwell]

Thanks for your pull request to Laravel!

Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.

If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!

[alejojperez]

@nunomaduro @taylorotwell Hey Taylor, I think that you should reconsider your decision here. This PR is very much needed to add resource template capabilities to the MCP package. Unless you have already planned internally to add resource template support, I would appreciate it if you could reconsider your decision here.

[alankpax]

Hi, why is this PR closed if it is only delayed ? This feature will be more and more asked.

[pushpak1300]

@alankpax this is released in v0.4.0 by #113