Browse
→ Code & Dev
→ Laravel MCP Bridge
Laravel MCP Bridge
Exposes selected Laravel routes and resources as MCP tools while retaining application middleware, validation and policies. Separate operator endpoints can expose explicitly permitted commands, jobs and models. Needs PHP 8.3 or later and a supported Laravel version. Scoped tokens control access; audit exposed tools before enabling writes or changing the default opt-in mode. Public repository created November 1, 2026.
MCP unverified
Integration
| Transport | http |
| Auth | api-key |
| Endpoint | http://localhost:8000/mcp |
| Install | In a compatible Laravel application run composer require kayedspace/laravel-mcp-bridge and php artisan mcp-bridge:install; configure HasMcpTokens, mark intended tools, inspect mcp-bridge:tools --refused and issue a restricted token; replace the illustrative localhost URL with your application /mcp endpoint |
Use Cases
| 01 | Expose selected application routes to an agent |
| 02 | Keep operator tools separate from user tools |
| 03 | Inspect generated tool contracts before deployment |
Tags
laravel api-tools scoped-tokens self-hosted
Machine-readable: /api/servers.json
· JSON-LD schema embedded in <head>