About Laravilt
Laravilt is a read-only MCP server for AI assistants working with Laravilt. It provides current package documentation, release details, and plugin and installation guidance.
Key features
- 01Browse Laravilt packages and versions
- 02Search and read documentation
- 03Retrieve changelogs and requirements
- 04Access plugin and installation guides
- 05Use synced MCP resources and prompt
Use cases
- 01Check package requirements before installation
- 02Find guidance for building a Laravilt plugin
- 03Review recent package changes
- 04Look up Vue or React frontend documentation
MCP support
Exposes package and documentation tools, resources, and the `build-resource` prompt to MCP clients over streamable HTTP. The public endpoint requires no authentication and is rate limited per IP.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.laravilt.com/mcpclaude mcp add --transport http laravilt-laravilt https://mcp.laravilt.com/mcp{"mcpServers":{"laravilt-laravilt":{"type":"http","url":"https://mcp.laravilt.com/mcp"}}}Open in Cursor{"servers":{"laravilt-laravilt":{"type":"http","url":"https://mcp.laravilt.com/mcp"}}}Open in VS Code{"mcpServers":{"laravilt-laravilt":{"type":"http","url":"https://mcp.laravilt.com/mcp"}}}{"mcpServers":{"laravilt-laravilt":{"serverUrl":"https://mcp.laravilt.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
9This tool takes no parameters.
Details
From the project README
Laravilt MCP
A public, read-only Model Context Protocol server that gives AI assistants the latest Laravilt documentation, READMEs, changelogs and released versions of every laravilt/* package, including the plugin system and the Vue/React frontends.
Endpoint: https://mcp.laravilt.com/mcp (streamable HTTP, no authentication, rate limited per IP).
Connect
Claude Code
claude mcp add --transport http laravilt https://mcp.laravilt.com/mcp
Cursor / VS Code (.cursor/mcp.json or .vscode/mcp.json)
{
"mcpServers": {
"laravilt": { "type": "http", "url": "https://mcp.laravilt.com/mcp" }
}
}
Claude Desktop (through mcp-remote)
{
"mcpServers": {
"laravilt": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.laravilt.com/mcp"] }
}
}
Any other client: use the streamable HTTP URL https://mcp.laravilt.com/mcp.
Tools
| Tool | What it returns |
|---|---|
list-packages | Every Laravilt package with description, latest version, release date, install command and repository |
get-package | One package: README summary, latest version, requirements, frontend notes (Vue and React), docs index, recent changelog |
search-docs | Ranked documentation snippets with paths and GitHub links (optionally scoped to a package) |
read-doc | A full document, paginated for long pages |
list-docs | The documentation tree, for one package or all |
get-latest-versions | A package => version map and a ready-to-paste composer require line |
get-changelog | Recent changelog entries for a package |
plugin-development-guide | How to build Laravilt plugins, assembled from the laravilt/plugins docs |
installation-guide | Installing Laravilt on Laravel 13 with php artisan laravilt:install --stack=vue|react |
Resources: laravilt://packages and laravilt://docs/{package}/{path} for every synced document. Prompt: build-resource.
How content stays current
php artisan laravilt:sync scans the laravilt GitHub organization, downloads each package's default branch as a tarball, indexes README.md, CHANGELOG.md, composer.json and every Markdown file under docs/, and records released versions from Packagist. Unchanged commits are skipped. The scheduler runs it every 30 minutes, and a GitHub webhook (POST /webhooks/github, signed with GITHUB_WEBHOOK_SECRET) queues a sync of the pushed repository immediately.
Local development
composer install
cp .env.example .env && php artisan key:generate
touch database/database.sqlite
php artisan migrate
php artisan laravilt:sync
php artisan serve
Then open http://127.0.0.1:8000 for the landing page, or point an MCP client at http://127.0.0.1:8000/mcp.
php artisan test
vendor/bin/pint
Configuration
| Variable | Default | Purpose |
|---|---|---|
APP_URL | Public URL, e.g. https://mcp.laravilt.com | |
LARAVILT_GITHUB_ORG | laravilt | Organization scanned for packages |
LARAVILT_EXCLUDED_REPOS | mcp,laravilt.com,laravilt-dev,.github | Repositories that are not packages |
GITHUB_TOKEN | Optional; raises the GitHub API rate limit | |
GITHUB_WEBHOOK_SECRET | Required to accept push webhooks | |
LARAVILT_SYNC_INTERVAL | 30 | Minutes between scheduled syncs |
LARAVILT_SEARCH_DRIVER | auto | auto, fts (SQLite FTS5) or like |
LARAVILT_DOC_PAGE_SIZE | 16000 | Characters per read-doc page |
LARAVILT_RATE_LIMIT | 120 | MCP requests per minute per IP |
LARAVILT_MCP_PATH | mcp | Path of the MCP endpoint |
TRUSTED_PROXIES | Proxy IPs/CIDRs (set when behind a reverse proxy) |
Deployment
composer install --no-dev --optimize-autoloader, create.envfrom.env.example,php artisan key:generate,php artisan migrate --force.- Run
php artisan laravilt:synconce. - Run the scheduler every minute (
php artisan schedule:run) and a queue worker for webhook-triggered syncs (php artisan queue:work, orQUEUE_CONNECTION=sync). - Serve
public/with PHP-FPM behind your web server or reverse proxy, and setTRUSTED_PROXIES. - In each Laravilt repository (or the organization), add a webhook to
https://mcp.laravilt.com/webhooks/githubfor push events, using the same secret.
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.