Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Laravilt docs, packages and plugins for agents: a Laravel admin panel on Inertia with Vue or React.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.laravilt.com/mcpRun this in your terminal
claude mcp add --transport http laravilt https://mcp.laravilt.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"laravilt": {
"url": "https://mcp.laravilt.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"laravilt": {
"type": "http",
"url": "https://mcp.laravilt.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.laravilt.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account laravilt, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 26 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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).
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.
| 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.
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.
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
| 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) |
composer install --no-dev --optimize-autoloader, create .env from .env.example, php artisan key:generate, php artisan migrate --force.php artisan laravilt:sync once.php artisan schedule:run) and a queue worker for webhook-triggered syncs (php artisan queue:work, or QUEUE_CONNECTION=sync).public/ with PHP-FPM behind your web server or reverse proxy, and set TRUSTED_PROXIES.https://mcp.laravilt.com/webhooks/github for push events, using the same secret.MIT