页面 · Laravilt
MCP
Connect AI agents to Laravilt with the hosted MCP server and the per-package local servers.
Laravilt supports the Model Context Protocol (MCP) in two ways:
- The hosted Laravilt MCP server at
https://mcp.laravilt.com/mcp. It gives AI agents read-only access to the latest docs, READMEs, changelogs and versions of every Laravilt package. You install nothing. - Local MCP servers shipped inside individual packages. They run in your app through
laravel/mcpand can generate code in your project.
Hosted server
URL: https://mcp.laravilt.com/mcp (streamable HTTP, public, read-only, rate limited per IP)
Claude Code
Other MCP clients
Any client that supports remote HTTP servers (Cursor, VS Code, Claude Desktop, Windsurf and others) can use the URL. A typical mcp.json entry:
Tools
| Tool | Description |
|---|---|
list-packages | Every laravilt/* package with description, latest version, release date, install command and GitHub URL |
get-package | Details for one package: README summary, requirements, Vue/React support, docs index and recent changes |
search-docs | Full-text search across all docs, READMEs and changelogs (query, optional package, limit) |
read-doc | Read a full document (package, path, optional page) |
list-docs | The documentation tree for one package, or all packages |
get-latest-versions | Latest version of every package plus ready-to-paste composer require lines |
get-changelog | Release history and changelog entries for a package (package, optional limit) |
installation-guide | Step-by-step install for a new Laravel 13 app (stack: vue or react) |
plugin-development-guide | Guide to building plugins with laravilt:plugin and laravilt:make |
The server also exposes the laravilt-packages and laravilt-doc resources and a build-resource prompt.
Example prompts:
Local package servers
Several packages include an MCP server class in src/Mcp. They need laravel/mcp:
Register the servers you want in routes/ai.php:
Then start one with php artisan mcp:start laravilt-forms or add it to your client's .mcp.json:
php artisan laravilt:install-mcp (from laravilt/plugins) does all of this for the plugins server. See Plugins MCP.
| Package | Server class | Tools | Page |
|---|---|---|---|
laravilt/laravilt | Laravilt\Laravilt\Mcp\LaraviltServer | list-packages-tool, package-info-tool, install-laravilt-tool, make-user-tool, search-docs-tool | below |
laravilt/panel | Laravilt\Panel\Mcp\LaraviltPanelServer | search-docs-tool, list-panel-features-tool, get-resource-info-tool | Panel |
laravilt/forms | Laravilt\Forms\Mcp\LaraviltFormsServer | generate-form-tool, search-docs-tool | Forms |
laravilt/tables | Laravilt\Tables\Mcp\LaraviltTablesServer | generate-table-tool, search-docs-tool | Tables |
laravilt/schemas | Laravilt\Schemas\Mcp\LaraviltSchemasServer | generate-schema-tool, search-docs-tool | Schemas |
laravilt/auth | Laravilt\Auth\Mcp\LaraviltAuthServer | search-docs-tool, get-event-info-tool, list-auth-methods-tool | Auth |
laravilt/plugins | Laravilt\Plugins\Mcp\LaraviltPluginsServer | 7 plugin tools | Plugins |
Local tool names come from their class names (for example GenerateFormTool becomes generate-form-tool).
Core server (laravilt/laravilt)
| Tool | Arguments | Description |
|---|---|---|
list-packages-tool | none | Installed Laravilt packages and versions |
package-info-tool | package | Details about one package |
install-laravilt-tool | force, skip_migrations, skip_npm | Install and configure Laravilt |
make-user-tool | name, email, password | Create an admin user |
search-docs-tool | query, package | Search the bundled docs |
Security
Local servers run with your application's permissions and can write files. Only register them in development and keep .mcp.json out of shared environments. The hosted server is read-only.