A
licenseA
qualityC
maintenanceMCP server exposing the Laravel Forge API v2 with curated tools for deploys, logs, env, and services plus universal access to all 273 operations.
28
Apache 2.0
Laravel MCP Server
by dok4everak47
Related Servers
Alternatives to Laravel MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables developers to expose any dev tool as a safe, audited MCP server with permission tiers, audit logging, and automatic argument validation.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to introspect a Laravel application's routes, models, controllers, migrations, and more through the Model Context Protocol, running locally via php artisan commands and filesystem scanning.6 npmMIT
- AlicenseNot gradedqualityDmaintenanceIntegrates with the Laravel Forge API to provide comprehensive management of servers and sites. It enables users to perform health checks, monitor logs, create resources, and execute deployment tasks through MCP-compliant tools.15 npm2MIT
- AlicenseNot gradedqualityBmaintenanceMCP server enabling AI assistants to manage Laravel Forge through the full Forge API v2, with ~270 tools for servers, sites, deployments, databases, backups, and more.14 npmMIT
- AlicenseAqualityDmaintenanceMCP server for structured Laravel project planning. Scans projects, creates tickets, and exports as JSON.39 npmMIT
TDQS
B3.4/5.0
Scored across 23 tools
Disambiguation4/5
Most tools have clearly distinct purposes, but there is overlap between envInfo/envInfoSafe and between migrationAnalyzer/schema for inspecting database structure. The three generators (crudGenerator, createFeature, apiGenerator) also have similar scopes, though descriptions clarify differences.
Naming Consistency2/5
Tool names use inconsistent patterns: some are camelCase verbs (runTest, makeModel), some are noun-first (envInfo, configGet), some are single nouns (artisan, model, log), and some are compound names (migrationAnalyzer, crudGenerator). No consistent verb_noun convention.
Tool Count3/5
23 tools is on the heavy side; while each has a purpose, the server covers many development workflows, making it borderline but manageable. Not excessive enough for a 2, but more than the typical well-scoped server.
Completeness4/5
The toolset covers a wide range of Laravel tasks: environment info, migrations, schema inspection, code generation, testing, debugging, and project context. Minor gaps like missing seeding/rollback commands can be worked around via artisan, so not severely incomplete.
Maintenance
ActivitySlowing
ResponsivenessNo issues