Laravel Forge MCP. Manage deployments and server states via chat.
Laravel Forge MCP lets you manage entire web application ecosystems directly through your AI agent's chat window. You can list all connected droplets, check internal structures, deploy site scripts safely, and query databases linked to specific domains—all without leaving the conversation.
Give Claude and any AI agent real-world access
List all connected droplets and inspect the internal structures of your deployed sites.
Send a deployment script to a specific repository site, watching the output as it executes.
Query active databases associated with any connected domain cluster.
Examine the daemon configurations and queue workers running on a tracked site.
Ask an AI about this
Waiting for input…
What AI agents can do with Laravel Forge: 9 Tools for Ops
Use these tools to perform deep devops functions like running site deployments, listing server inventory, or checking database configurations through your agent.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Laravel Forge MCPDeploy Site
Runs a deployment script queue to push updates to an entire repository site.
Get Server
Pulls detailed information on one specific server droplet instance.
Get Site
Retrieves specifics for a particular website layout running on a given server.
List Databases
Lists all active databases mounted to a Forge server instance.
List Recipes
Retrieves available custom shell recipes within your organizational team limits.
List Servers
Gathers the master list of every connected Forge server instance.
List Sites
Lists all websites that are mounted to a specific server droplet.
List Ssh Keys
Retrieves active physical access keys attached to the root server.
List Workers
Gets the queue worker configurations that are currently running on a tracked site.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Laravel Forge, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Laravel Forge. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Pain of Context Switching
Today, pushing out an update feels like juggling three different tools. You start in the Git client to pull commits. Then you jump to the dashboard to confirm which server droplet needs updating. After that, you open a separate database tool just to ensure the schema is ready for the new code. It's a constant stream of switching tabs and copying credentials.
With this MCP, the whole process collapses into one chat window. You tell your agent what to do, and it handles the sequence: checking server status, listing connected databases, and running `deploy_site`. You get back confirmation that the job is done, without ever leaving your conversation.
Get Server Data with `get_server`
Manually checking a server's status means logging into multiple portals and digging through different metrics pages to piece together what’s wrong. You might find the uptime, but you'll miss critical details about worker configurations or active key lists.
Now, just ask your agent for detailed data on that specific droplet using `get_server`. It pulls the complete metadata in one go. You know exactly what you're working with.
What Laravel Forge MCP does for your AI
This MCP connects your developer account to an AI agent, turning complex deployment tasks into natural conversations. Instead of jumping between a console, a dashboard, and a database client, you talk to your agent. You tell it what needs fixing or deploying, and it handles the backend work. It checks server statuses, lists connected databases for any given domain, and runs full site deployment scripts—all in one go.
This is how modern development ops works: talking through complex processes instead of clicking through menus. With Vinkius, this MCP puts that entire suite of devops tools right at your fingertips, letting you act like a senior engineer without having to be one.
019d75c4-c4d2-7077-ad13-08125e219f59 How to set up Laravel Forge MCP
The bottom line is, you treat complex infrastructure management like a simple chat command.
Subscribe to this MCP endpoint in your AI client.
Provide your core Laravel Forge API token string for authentication.
Ask your agent to execute the required devops tasks through natural conversation.
Who uses Laravel Forge MCP
This MCP is for experienced technical roles—DevOps Engineers and Lead Developers who get bogged down in manual dashboards. You're the person tired of switching context between SSH, Git, and database clients just to roll out a simple patch.
Runs site deployments or checks worker statuses natively during sprint reviews using chat commands.
Instantly confirms SSH key metadata and active daemon configurations across multiple environments without logging into the console.
Audits entire physical networks or checks system-level structures by running commands through your AI agent instead of writing shell scripts.
Benefits of connecting Laravel Forge MCP
Avoid jumping between multiple dashboards. You can check the status of all connected droplets, list websites, and view SSH keys—all from a single conversational interface using list_servers, list_sites, and list_ssh_keys.
Deployment is instant. Instead of manually executing scripts, you simply tell your agent to run a deployment script via deploy_site. The agent handles the queue execution and tracks output automatically.
Database management becomes conversational. You never have to guess which cluster is live; just ask your agent to list databases using list_databases and get the details immediately.
Audit worker processes effortlessly. Need to know if a background job is stuck? Use list_workers to check queue configurations running on any tracked site, ensuring nothing drops off.
System visibility improves dramatically. If you need deep context, your agent can pull detailed data on a specific droplet with get_server, or look up the specifics of an exact site layout using get_site.
Laravel Forge MCP use cases
Rolling out a major feature to staging
A developer needs to push code changes to the pre-production environment. They prompt their agent: 'Deploy the pending commits directly to site 5210 on server 1205.' The agent executes deploy_site, reports success, and confirms the new payload is live.
Investigating a slow background task
The application suddenly slows down because jobs aren't processing. A lead developer asks their agent to check the queue workers using list_workers. The agent immediately reports finding two active Queue workers, confirming if they are handling the necessary payloads.
Onboarding a new team member
A sysadmin needs a complete overview of the infrastructure. They ask their agent to list all connected servers using list_servers, which provides the master inventory, followed by listing every site on those machines via list_sites.
Verifying access for an external vendor
A developer needs to confirm what physical keys are available for a new service connection. They simply ask their agent and it uses list_ssh_keys to retrieve the active physical access key metadata.
Laravel Forge MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Copying commands from documentation
Manually reading a guide, copying a complex series of shell commands, and pasting them into a terminal session. This is slow and error-prone.
Just tell your agent what you want done. For example, instead of typing out the deployment script for a site, just ask the agent to deploy_site and let it handle the rest.
Guessing which server has data
A developer is unsure if their application database lives on Server A or Server B and spends minutes querying network maps.
Start by asking the agent to list_servers to see your whole inventory. Then, use list_databases to query all active databases across the entire connected environment.
Forgetting necessary prerequisites
Trying to deploy a site without checking if the underlying infrastructure or worker processes are running correctly.
Before deploying, always check the health. Run list_workers first. If those look good, then proceed with your deployment via deploy_site.
When to use Laravel Forge MCP
Use this MCP if you need to manage entire web stacks—from databases and worker queues up through live deployments—all without leaving the chat interface. You're looking for conversational control over complex infrastructure operations. Don't use it if your only goal is basic code review or writing simple Python scripts; that’s better handled by a pure coding agent. If you just need to look at one specific file, any general-purpose reading tool will work. But if the task involves coordinating multiple layers—like confirming which server hosts a site, checking its associated database, and then deploying new code to it—this MCP is your single source of truth.
Frequently asked questions about Laravel Forge MCP
Can I use Laravel Forge MCP to list all my servers? +
Yes, you can. Use the list_servers tool to retrieve a master inventory of every connected Forge server instance in one command.
How do I deploy code using the Laravel Forge MCP? +
You execute deployments with the deploy_site tool. This runs the script queue and manages the full deployment process for your specific repository site.
What if I need to check my database settings? +
Use list_databases. This tool lists all active databases that are mounted onto a specific Forge server, keeping your data sources organized and visible.
Does Laravel Forge MCP help me find SSH keys? +
Yes. The list_ssh_keys tool lets you retrieve the list of all active physical access keys attached to your root server for auditing purposes.
Can I check which workers are running on a site? +
You use the list_workers tool. It checks and reports on the queue worker configurations currently executing tasks on any tracked site, giving you full visibility into background jobs.