Add example of registering MCP Tool in a Server#164
Merged
pushpak1300 merged 4 commits intolaravel:mainfrom Feb 24, 2026
Merged
Add example of registering MCP Tool in a Server#164pushpak1300 merged 4 commits intolaravel:mainfrom
pushpak1300 merged 4 commits intolaravel:mainfrom
Conversation
Contributor
Author
|
Note for maintainers: The CI failure is due to an unused import in This PR only adds a documentation snippet showing how to register an MCP Tool in a Server. |
Member
|
Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR improves the MCP Development skill documentation by adding a minimal, clear example of how to register a previously created MCP Tool in a Server.
Previously, the documentation showed how to create MCP tools using artisan commands and provided an example of a Tool class, but it did not show how to expose that Tool via a Server. This caused a gap in the developer flow.
Changes included:
This small addition improves clarity and helps developers quickly understand the full MCP Tool workflow, increasing the value of the skill documentation without affecting existing snippets.