---
title: 'LaraBench MCP'
description: 'Connect Claude, Codex, Cursor, and other MCP clients to LaraBench. Search recent Laravel jobs and news, or use local tools with your own apps.'
canonical_url: 'https://larabench.com/mcp-server'
md_url: 'https://larabench.com/mcp-server.md'
last_updated: '2026-07-28'
---
# LaraBench MCP

> Connect Claude, Codex, Cursor, and other MCP clients to LaraBench. Search recent Laravel jobs and news, or use local tools with your own apps.

## Direct Answer

LaraBench has two MCP servers. The public server is a read-only endpoint at `https://larabench.com/mcp` for recent Laravel jobs, articles, and package releases. The desktop server runs inside the LaraBench app and reads only the connections, saved snippets, run history, and logs you expose.

## Public MCP

- Endpoint: `https://larabench.com/mcp`.
- Transport: remote HTTP MCP for compatible clients.
- Authentication: none.
- Scope: public LaraBench jobs, news articles, and package releases.
- Freshness: server-enforced last 7 days.
- URLs: every result points to `larabench.com`.
- Writes: none.

### Public MCP Tools

- `search_laravel_jobs`: search recent Laravel jobs. Inputs include `query`, `technologies`, `workArrangement`, `locations`, `countries`, `salaryMinimum`, `salaryCurrency`, `seniority`, `employmentTypes`, and `limit`.
- `search_laravel_news`: search recent Laravel ecosystem articles and package releases. Inputs include `query`, `types`, `topics`, `projects`, `packages`, `sources`, `channel`, and `limit`.

### Add The Public MCP

Use these values in an MCP client that supports remote HTTP MCP servers:

```json
{
  "mcpServers": {
    "larabench-public": {
      "url": "https://larabench.com/mcp"
    }
  }
}
```

Some clients expose this as a form instead of JSON. In that case, use `larabench-public` as the name, `https://larabench.com/mcp` as the URL, and leave authentication empty.

#### Claude Code

```shell
claude mcp add --transport http --scope user larabench-public https://larabench.com/mcp
```

#### Codex

```shell
codex mcp add larabench-public --url https://larabench.com/mcp
```

#### Cursor

Use the Add to Cursor button on the HTML page to open Cursor's MCP install prompt.

## Desktop MCP

The desktop MCP is for agents working with your own Laravel applications. It runs through the local LaraBench app and only exposes connections you allow.

### Desktop Read And Search Tools

- `list_connections`: list exposed Laravel connections and each connection's MCP access level.
- `list_saved_items`: browse saved Tinker snippets and Artisan commands by folder, tag, search, kind, or pinned state.
- `get_run_history`: read recent LaraBench runs with code, command, output, exit code, duration, and query count.
- `read_logs`: list Laravel log files or read entries from a selected file.
- `search_laravel_jobs`: search LaraBench jobs. Free searches cover 7 days; signed-in Premium extends to 90 days.
- `search_laravel_news`: search LaraBench news and package releases. Premium extends to 90 days.
- `get_developer_profile`: fetch your saved developer profile and the current jobs filter vocabulary when signed in.

### Desktop Run And Save Tools

- `run_snippet`: run a Tinker snippet against a connection and return output, exit code, duration, and query analysis.
- `run_artisan`: run an Artisan command against a connection. Artisan commands need Full access because they cannot be dry-run safely.
- `run_saved_item`: run a saved snippet or Artisan command, filling any `{placeholder}` values first.
- `save_snippet`: save a Tinker snippet or Artisan command back to your LaraBench library.

Run and save tools need LaraBench Premium and the app open.

### Add The Desktop MCP

1. Install and open LaraBench.
2. Create the local, Docker, or SSH connections you want to expose.
3. Open the MCP Server page inside the app.
4. Set each connection to Off, Read only, Dry run, or Full.
5. Click the button for Claude Code, Claude Desktop, Codex, or Cursor, or use Show config for another MCP client.

The generated config points at the LaraBench app with `--mcp-stdio`, for example:

```json
{
  "mcpServers": {
    "larabench": {
      "command": "path shown by LaraBench",
      "args": ["--mcp-stdio"]
    }
  }
}
```

## Safety

- Public MCP is anonymous and read-only.
- Desktop connections use explicit AI access levels: Off, Read only, Dry run, or Full.
- Production connections start hidden from MCP.
- Dry run cannot be loosened by a tool call.
- A write against Full production still waits for human confirmation in LaraBench.
- AI-driven desktop runs are recorded in History.

## Which One To Use

- Use public MCP when an agent needs recent Laravel jobs, articles, or releases and does not need your desktop app.
- Use desktop MCP when an agent needs your own Laravel connections, logs, saved snippets, run history, or controlled code execution.

## Related Pages

- [Public MCP endpoint](https://larabench.com/mcp)
- [Desktop MCP docs](https://larabench.com/docs/advanced-usage/mcp-server)
- [AI agent Laravel MCP article](https://larabench.com/blog/ai-agent-laravel-mcp)
- [Laravel jobs](https://larabench.com/laravel-jobs)
- [Laravel news and releases](https://larabench.com/news)

## Canonical Page

- [HTML page](https://larabench.com/mcp-server)
- [Markdown mirror](https://larabench.com/mcp-server.md)

## Glossary

- [Laravel workflow glossary](https://larabench.com/docs/reference/glossary)

## Sitemap

See the full [sitemap](https://larabench.com/sitemap.md) for all public pages.