// public mcp
Search recent Laravel jobs, news, and releases.
The public server needs no account or desktop app. It is read-only, limits every search to the last 7 days, and returns LaraBench detail pages.
https://larabench.com/mcp// mcp for laravel
Use the public MCP to search Laravel jobs, ecosystem news, and package releases from the last 7 days. Use the desktop MCP to give Claude, Codex, Cursor, or another client controlled access to your own Laravel connections, logs, saved items, and run history.
// public mcp
The public server needs no account or desktop app. It is read-only, limits every search to the last 7 days, and returns LaraBench detail pages.
https://larabench.com/mcp// desktop mcp
The desktop server exposes only the LaraBench connections and local data you select. Premium adds run and save tools, with a separate access level for every connection.
Download LaraBench// choose the right server
Best for
// public Recent Laravel jobs, articles, and package releases.
// desktop Your Laravel connections, logs, saved items, and run history.
Install
// public No desktop app. Add the remote URL in a compatible MCP client.
// desktop Install LaraBench and connect your AI client from the app.
Data
// public Public LaraBench jobs and news only.
// desktop Your exposed connections, saved library, history, logs, jobs, news, and profile.
Writes
// public None. Read-only.
// desktop Premium tools can run snippets, run Artisan, run saved items, and save snippets.
URLs
// public Every result points to larabench.com.
// desktop Local app context plus LaraBench jobs/news URLs.
// public tools
These tools return compact summaries plus LaraBench detail URLs. They never return external apply links, source article URLs, registry URLs, saved snippets, logs, or anything from a desktop app.
Search recent Laravel jobs indexed by LaraBench. Results are capped to the last 7 days and link to LaraBench job pages.
Search recent Laravel ecosystem articles and package releases. Results are capped to the last 7 days and link to LaraBench news pages.
// desktop tools
The desktop MCP reads only the LaraBench data and connections you expose. Run and save tools require Premium, the open app, and permission on the selected connection.
List the Laravel connections exposed to AI tools and show each connection's access level.
Browse saved Tinker snippets and Artisan commands by folder, tag, search, kind, or pinned state.
Read recent LaraBench runs with code, command, output, exit code, duration, and query count.
List Laravel log files or read entries from a selected file. SSH and Docker logs need the app open.
Search LaraBench jobs from the desktop MCP. Free searches cover 7 days; signed-in Premium extends to 90 days.
Search LaraBench news and package releases from the desktop MCP. Premium extends the search window to 90 days.
Return your saved developer profile and the current job filter options when you are signed in.
Run a Tinker snippet against a connection and return output, exit code, duration, and query analysis.
Run an Artisan command against a connection. Artisan runs need Full access because they cannot be dry-run safely.
Run a saved snippet or Artisan command, filling any {placeholder} values first.
Save a Tinker snippet or Artisan command back to your LaraBench library.
// add to your agent
Cursor can open the public server in an install prompt. The Claude and Codex buttons copy their official CLI commands. The desktop app writes its local stdio config for each supported client.
No API key or account is required.
{
"mcpServers": {
"larabench-public": {
"url": "https://larabench.com/mcp"
}
}
}{
"mcpServers": {
"larabench": {
"command": "path shown by LaraBench",
"args": ["--mcp-stdio"]
}
}
}// safety
Public MCP results are anonymous and read-only. They are limited to recent public LaraBench jobs, news, and release pages.
Desktop connections start from explicit AI access levels: Off, Read only, Dry run, or Full. Production starts hidden.
Dry run cannot be loosened by a tool call. A write against Full production still waits for a human confirmation in LaraBench.
AI-driven desktop runs are recorded in History with the same output, exit code, timing, and query context as your own runs.