Download the PHP package desino/mcp-framework-boilerplate without Composer

desino/mcp-framework-boilerplate

Laravel scaffolding package that publishes the Desino MCP reference application into your host app via a single Artisan command — similar to desino/boilerplate.

After installation, MCP code lives in your application (app/, routes/, resources/, etc.) and can be edited like first-party code.

What gets published

• MCP server at /mcp (routes/ai.php) with bearer token authentication
• Admin UI to manage MCP tools (/mcp_tools)
• Built-in library tools (GitHub, PM tool, project resolver)
• Custom MCP tool generator and stubs
• Models, migrations, services, views, and translations

Requirements

• PHP ^8.3
• Laravel ^13
• laravel/mcp
• desino/boilerplate

Installation

1. Require the package

For local development from this repository:

2. Publish Desino boilerplate (if not already done)

3. Publish MCP boilerplate

The command always overwrites existing files, so re-running it resets published MCP files back to the packaged versions. Keep local edits to published files under version control before re-running.

This copies MCP scaffolding into your application:

The command also merges:

• MCP tool routes into routes/web.php (inside the checkIfAdmin middleware group)
• MCP translation keys into lang/en/messages.php
• verifyMcpToken middleware alias into bootstrap/app.php

4. Configure environment

5. Run migrations

Tables created:

• mcp_projects
• mcp_tools
• mcp_audit_logs

MCP tool ordering:

• The mcp_tools table has an ordering column.
• The installer adds the ordering column (and backfills existing rows).
• New tools default to the last position (ordering = max + 1).

6. Add navigation link (optional)

Add an MCP Tools menu item to your layout:

Usage

MCP endpoint

Active tools registered in the admin UI are exposed at:

MCP tool execution order:

When the MCP server handles a request, it returns active tools ordered by mcp_tools.ordering ascending (then by id to break ties).

Admin UI routes

Ordering in the tools list:

• The /mcp_tools list shows an Order column.
• Use the move up / move down arrows to open a confirmation modal, then submit the reorder form with a loading screen.
• On successful update, the page reloads and the MCP server will follow the new order immediately.

Library tools

• coding_standard — Review code against selected coding standard rules
• support.resolve_project — Resolve project details from a project code
• pmtool.search_tickets — Smart PM tool ticket search
• github.search_code — GitHub code search
• github.read_file — Read a file from GitHub
• github.recent_commits — List recent commits
• database.safe_select — Run safe read-only SQL SELECT queries

Coding standard rules

The coding_standard library tool builds its description from rules you select in the admin UI, so AI clients only ever see the instructions for the enabled rules.

Published rules in app/CodingStandardRules/:

• DESINO_PSR_001 — PSR-1, PSR-4 and PSR-12 coding style
• LARAVEL_CONTROLLER_001 — Controller structure and responsibility
• LARAVEL_DATABASE_001 — Migration structure and reversibility
• LARAVEL_ELOQUENT_002 — Model class and query standards
• LARAVEL_ROUTE_001 — Route definition and naming conventions
• PHP_FUNCTIONS_001 — PHP function usage standards
• SECURITY_SQL_INJECTION_001 — SQL injection prevention

To add a rule, drop a class into app/CodingStandardRules/ that implements App\Contracts\CodingStandardRule. The class name becomes the rule ID shown in the admin UI, and it is picked up automatically — no registration step.

Custom tools

Custom tools are generated into app/Mcp/Tools/ when created from the admin UI.

Configuration

Key options in config/my_mcp.php:

Package vs application code

This package is a thin installer. It only ships:

• MakeMcpBoilerplateCommand (php artisan make:desino-mcp-framework-boilerplate)
• Application stubs under src/stubs/

All runtime MCP logic runs from your host application's app/ directory after publishing.

License

MIT — see LICENSE.