Skip to main content
Glama
dok4everak47

Laravel MCP Server

by dok4everak47

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PHP_PATHNoPHP executable pathphp
LARAVEL_PROJECT_PATHNoPath to Laravel projectprocess.cwd()

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
artisanA

Run a Laravel artisan command. Returns stdout and stderr.

migrateStatusA

Show the status of Laravel migrations. Lists which migrations have been run and which are pending.

envInfoA

Show Laravel environment info: APP_ENV, APP_DEBUG, and database connection status.

cacheB

Manage Laravel caches: clear all caches, or cache config/routes for performance.

configGetA

Get a Laravel config value by key (e.g. 'app.name', 'database.default', 'mail.default').

schemaA

Inspect the Laravel database schema: list all tables, or show column details for a specific table.

modelA

List Eloquent models in the Laravel application by scanning app/Models and verifying they extend Model.

logA

View recent entries from the Laravel log file (storage/logs/laravel.log).

routeListB

List Laravel routes with optional filtering by name or URI

runTestA

Run PHPUnit tests with optional filter

envInfoSafeA

Read Laravel environment info, filtering out sensitive values (keys, passwords, tokens)

frontendScannerA

Scan Laravel frontend structure: views, JS, CSS files

makeModelB

Create a new Eloquent model class

makeControllerB

Create a new controller class

makeMigrationB

Create a new migration file

migrationAnalyzerA

Parse Laravel migration files and extract database schema (columns, types, foreign keys)

composerAnalyzerA

List Laravel project dependencies from composer.json and composer.lock

crudGeneratorA

Generate full CRUD for a Laravel entity: migration, model, controller, request, route, test, and run tests

createFeatureB

Generate complete Laravel feature: migration, model, controller, requests, routes, blade views, tests

debugWorkflowA

Analyze a Laravel error: locate file, read context, diagnose common issues, suggest fixes

apiGeneratorB

Generate REST API for a Laravel entity: migration, model, API controller, routes, tests

projectContextA

Get comprehensive Laravel project context (version, models, routes, packages, structure)

intentPlannerA

Parse a natural language development request, generate an execution plan, and optionally execute it

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Laravel Project ContextComprehensive project context: version, models, routes, packages

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

ActivityMaintained
ResponsivenessNo issues