Laravel Forge

Laravel Forge MCP Connector for Claude

A+

Manage Laravel Forge servers, orchestrate site deployments, and query databases directly from your AI agent.

9 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Connect your Laravel Forge developer account to an AI agent to execute complex devops tasks natively in chat.

What you can do

  • Server Ecosystems — List all connected drops, inspect internal structures, and check status
  • Deployments — Safely dispatch site deployment scripts and watch output structures
  • Database Configurations — Query connected DB clusters linked to given domains
  • Worker Operations — Expose active daemon configurations routing jobs under your servers

How it works

  1. Subscribe dynamically to this endpoint
  2. Provide your core Laravel Forge API token string
  3. Engage your new devops engineer via Cursor or Claude

Who is this for?

  • DevOps Engineers — run deployments natively through chat commands during sprint reviews
  • Lead Developers — instantly check worker and SSH key metadata safely tracked inside Forge environments
  • System Admins — audit entire physical networks executing zero shell scripts
server-managementdeploymentphpautomationdatabase-managementweb-hosting

9 tools expose this connector's capabilities to your AI agent.

deploy_site

Command a deployment script queue to execute on a repository site

get_server

Retrieve detailed data on a specific server droplet

get_site

Look up specifics for an exact site layout on a server

list_databases

List active databases mounted on a Forge server

list_recipes

Retrieve available custom shell recipes within your organizational team limits

list_servers

Retrieve the master list of all connected Forge servers

list_sites

List websites mounted to a specific server

list_ssh_keys

Retrieve active physical access keys inserted on the root server

list_workers

Retrieve queue worker configurations executing on a tracked site

See how to talk to your AI agent using Laravel Forge.

Display all the cloud server instances operating in the fleet.

Here's what I observed... You have 2 droplets attached: 'Production Web' and 'Staging Loadbalancer'. Should I probe their sites?

Deploy the pending commits directly to staging site 5210 on server 1205.

Deploying package payload... Success! Forge emitted a validation flag kicking off the repository deployment routine on site 5210.

Check the active workers running on the production server.

Scanning worker processes... Found 2 active Queue workers on the Production Server handling redis payloads securely.

Subscribe, copy your active API Token (which you generate inside **Forge Dashboard → API**), and connect it. The integration expects standard connections so you can trigger real build routines natively without intricate pipelines or ssh logic.

Related Connectors