mcp-development
Skill108 starsChanged 5 months agoMITView on GitHub
Use this skill for Laravel MCP development. Trigger when creating or editing MCP tools, resources, prompts, servers, or UI apps in Laravel projects. Covers: artisan make:mcp-* generators, routes/ai.php, Tool/Resource/Prompt/AppResource classes, schema validation, shouldRegister(), OAuth setup, URI templates, read-only attributes, MCP debugging, MCP UI apps, the x-mcp::app Blade component, createMcpApp(), default AppResource handle() auto-infers view from class name, Response::view(), AppMeta/Csp/Permissions/appMeta() configuration, #[RendersApp] attribute, Library enum for CDN libraries (Tailwind, Alpine), and host theming via CSS variables. Use this whenever the user mentions MCP apps, MCP UI, interactive MCP resources, styling MCP apps with Tailwind or Alpine, or building visual interfaces for AI agents.
16 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- d-padmanabhan/agent-engineering-handbooktheir own version, first seen Nov 11, 2026
- relaticle/relaticleedited, first seen Oct 31, 2026
- asmamest/Nexus-Skillstheir own version, first seen Oct 15, 2026
- Dricle/eveiledited, first seen Oct 13, 2026
- SalesforceCommerceCloud/b2c-developer-toolingtheir own version, first seen Oct 8, 2026
- trypostit/trypostedited, first seen Oct 8, 2026
Used with
Projects with it also use cashier-stripe-development, passport-development and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
whisper-moneySkillcashier-stripe-development
Handles Laravel Cashier Stripe integration including subscriptions, webhooks, Stripe Checkout, invoices, charges, refunds, trials, coupons, metered billing, and payment failure handling. Triggered when a user mentions Cashier, Billable, IncompletePayment, stripe_id, newSubscription, Stripe subscriptions, or billing. Also applies when setting up webhooks, handling SCA/3DS payment failures, testing with Stripe test cards, or troubleshooting incomplete subscriptions, CSRF webhook errors, or migration publish issues.
Also in 5 projects that use this
datashamanSkillpassport-development
Develops OAuth2 API authentication with Laravel Passport. Activates when installing or configuring Passport; setting up OAuth2 grants (authorization code, client credentials, personal access tokens, device authorization); managing OAuth clients; protecting API routes with token authentication; defining or checking token scopes; configuring SPA cookie authentication; handling token lifetimes and refresh tokens; or when the user mentions Passport, OAuth2, API tokens, bearer tokens, or API authentication. Make sure to use this skill whenever the user works with OAuth2, API tokens, or third-party API access, even if they don't explicitly mention Passport.
Also in 6 projects that use this
gdarkoSkillfortify-development
ACTIVATE when the user works on authentication in Laravel. This includes login, registration, password reset, email verification, two-factor authentication (2FA/TOTP/QR codes/recovery codes), profile updates, password confirmation, or any auth-related routes and controllers. Activate when the user mentions Fortify, auth, authentication, login, register, signup, forgot password, verify email, 2FA, or references app/Actions/Fortify/, CreateNewUser, UpdateUserProfileInformation, FortifyServiceProvider, config/fortify.php, or auth guards. Fortify is the frontend-agnostic authentication backend for Laravel that registers all auth routes and controllers. Also activate when building SPA or headless authentication, customizing login redirects, overriding response contracts like LoginResponse, or configuring login throttling. Do NOT activate for Laravel Passport (OAuth2 API tokens), Socialite (OAuth social login), or non-auth Laravel features.
Also in 7 projects that use this
datashamanSkillconfiguring-horizon
Use this skill whenever the user mentions Horizon by name in a Laravel context. Covers the full Horizon lifecycle: installing Horizon (horizon:install, Sail setup), configuring config/horizon.php (supervisor blocks, queue assignments, balancing strategies, minProcesses/maxProcesses), fixing the dashboard (authorization via Gate::define viewHorizon, blank metrics, horizon:snapshot scheduling), and troubleshooting production issues (worker crashes, timeout chain ordering, LongWaitDetected notifications, waits config). Also covers job tagging and silencing. Do not use for generic Laravel queues without Horizon, SQS or database drivers, standalone Redis setup, Linux supervisord, Telescope, or job batching.
Also in 6 projects that use this
ownegoSkilllivewire-development
Use for any task or question involving Livewire. Activate if user mentions Livewire, wire: directives, or Livewire-specific concepts like wire:model, wire:click, wire:sort, or islands, invoke this skill. Covers building new components, debugging reactivity issues, real-time form validation, drag-and-drop, loading states, migrating from Livewire 3 to 4, converting component formats (SFC/MFC/class-based), and performance optimization. Do not use for non-Livewire reactive UI (React, Vue, Alpine-only, Inertia.js) or standard Laravel forms without Livewire.
Also in 5 projects that use this
m3ueSkillai-sdk-development
TRIGGER when working with ai-sdk which is Laravel official first-party AI SDK. Activate when building, editing AI agents, chatbots, text generation, image generation, audio/TTS, transcription/STT, embeddings, RAG, vector stores, reranking, structured output, streaming, conversation memory, tools, queueing, broadcasting, and provider failover across OpenAI, Anthropic, Gemini, Azure, Groq, xAI, DeepSeek, Mistral, Ollama, ElevenLabs, Cohere, Jina, and VoyageAI. Invoke when the user references ai-sdk, the `Laravel\Ai\` namespace, or this project's AI features — not for Prism PHP or other AI packages used directly.
Also in 5 projects that use this
Other versions16 projects use a version of this.
Word for word · 3
- Blair2004/NexoPOS★ 1.3k100% same
- whisper-money/whisper-money★ 1.1k100% same
- sbarbat/tentaclesauth★ 0100% same
Edited · 6
- coollabsio/coolify★ 66k98% same
- relaticle/relaticle★ 1.8k98% same
- Relaticle/relaticle★ 1.8k98% same
- trypostit/trypost★ 86898% same
- Dricle/eveil★ 1198% same
- datashaman/growth★ 1100% same
Wrote their own version · 7
- adeze/raindrop-mcp★ 188same name
- SalesforceCommerceCloud/b2c-developer-tooling★ 58same name
- d-padmanabhan/agent-engineering-handbook★ 20same name
- StacklokLabs/skills-mcp★ 4same name
- thejordanleopold/claude-code-skills-distilled★ 4same name
- asmamest/Nexus-Skills★ 1same name
- fabioc-aloha/alex-cognitive-architecture★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Use search-docs for detailed Laravel MCP patterns and documentation.
- Very specific: line 43
After creating primitives, register them in your server's $tools, $resources, or $prompts properties.
- Very specific: line 102
Check routes/ai.php for proper registration
- Distinctive: line 103
Test tool via MCP client
- Very specific: line 109
Not using search-docs for the latest MCP documentation
- Very specific: line 110
Not registering MCP server routes in routes/ai.php
- Very specific: line 111
Do not register ai.php in bootstrap.php.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
MCP Development
Documentation
Use search-docs for detailed Laravel MCP patterns and documentation.
For MCP UI apps (interactive HTML resources), read references/app.md — it covers the full architecture, host theming CSS variables, tool-to-UI linking patterns, library scripts (Tailwind, Alpine via Library), and real-world examples.
Basic Usage
Register MCP servers in routes/ai.php:
<!-- Register MCP Server -->use Laravel\Mcp\Facades\Mcp;
Mcp::web();Creating MCP Primitives
php artisan make:mcp-tool ToolName # Create a tool
php artisan make:mcp-resource ResourceName # Create a resource
php artisan make:mcp-prompt PromptName # Create a prompt
php artisan make:mcp-server ServerName # Create a server
php artisan make:mcp-app-resource DashboardApp # Create a UI app (2 files)
After creating primitives, register them in your server's $tools, $resources, or $prompts properties.
Tools
<!-- MCP Tool Example -->use Illuminate\Json\Schema\JsonSchema;
use Laravel\Mcp\Request;
use Laravel\Mcp\Response;
use Laravel\Mcp\Server\Tool;
class MyTool extends Tool
{
protected string $description = 'Describe what this tool does';
public function schema(JsonSchema $schema): array
{
return [
'name' => $schema->string()->description('The name parameter')->required(),
];
}
public function handle(Request $request): Response
{
$request->validate(['name' => 'required|string']);
return Response::text('Hello, '.$request->get('name'));
}
}Registering Primitives in a Server
<!-- Register Primitives in MCP Server -->use Laravel\Mcp\Server;
class AppServer extends Server
{
protected array $tools = [
\App\Mcp\Tools\MyTool::class,
];
protected array $resources = [
\App\Mcp\Resources\MyResource::class,
];
protected array $prompts = [
\App\Mcp\Prompts\MyPrompt::class,
];
}MCP UI Apps
For MCP UI apps, read references/app.md — it covers quick start examples, full architecture, AppMeta/Csp/Permissions, #[RendersApp] tool linking, library scripts (Tailwind/Alpine via Library), host theming CSS variables, and real-world patterns.
Verification
- Check
routes/ai.phpfor proper registration - Test tool via MCP client
Common Pitfalls
- Running
mcp:startcommand (it hangs waiting for input) - Using HTTPS locally with Node-based MCP clients
- Not using
search-docsfor the latest MCP documentation - Not registering MCP server routes in
routes/ai.php - Do not register
ai.phpinbootstrap.php; it is registered automatically - OAuth registration supports custom URI schemes (e.g.,
cursor://,vscode://) for native desktop clients viamcp.custom_schemesconfig
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

