Laravel Artisan MCP Server

Created By
entanglra year ago
A Model Context Protocol (MCP) server that enables secure execution of Laravel Artisan commands through Claude and other MCP clients.
Overview

What is Laravel Artisan MCP Server?

Laravel Artisan MCP Server is a Model Context Protocol (MCP) server that allows secure execution of Laravel Artisan commands through AI assistants like Claude. It serves as a bridge between AI and local Laravel applications, enabling natural language management of Laravel projects.

How to use Laravel Artisan MCP Server?

To use the server, clone the repository, set up a virtual environment, install dependencies, and configure environment variables for your Laravel project. You can then run the server and integrate it with Claude Desktop for command execution.

Key features of Laravel Artisan MCP Server?

  • Access to a single Laravel project directory
  • Automatic PHP location detection
  • Execution of only whitelisted Artisan commands
  • Viewing of available Artisan commands
  • Robust security measures including input validation

Use cases of Laravel Artisan MCP Server?

  1. Managing Laravel projects through natural language commands.
  2. Executing Artisan commands securely via AI assistants.
  3. Testing and validating commands in a controlled environment.

FAQ from Laravel Artisan MCP Server?

  • What is the purpose of this server?

It enables secure execution of Laravel Artisan commands through AI, enhancing project management.

  • Is it safe to use in production?

It is recommended for development or testing environments due to potential security risks.

  • What are the requirements?

Requires Python 3.10+, a Laravel project, and a compatible MCP client like Claude.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
entanglr
Star
1
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

5 hours ago
Alloy

2 days ago