Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Laravilt docs, packages and plugins for agents: a Laravel admin panel on Inertia with Vue or React.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.laravilt.com/mcp在终端中运行这条命令
claude mcp add --transport http laravilt https://mcp.laravilt.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"laravilt": {
"url": "https://mcp.laravilt.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"laravilt": {
"type": "http",
"url": "https://mcp.laravilt.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.laravilt.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 laravilt 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于26天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Safe Fetch
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
MCP server for fetching URLs, safe against SSRF, DNS rebinding, and redirect-to-internal attacks.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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