Laravel Forge MCP Server
Provides integration with Laravel Forge, a server management and deployment service for Laravel applications, enabling management of server resources, sites, and deployment processes.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Laravel Forge MCP Serverdeploy the latest changes to production"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Laravel Forge MCP Server
Mininum build to solve just one problem.
To build the MCP server, run:
npm install && npm run buildThis will compile the typescript files and produce a build directory plus it will output the json you can copy/paste into your MCP client (Claude Desktop, Windsurf, Cursor, etc.)
If all things go well, this will produce an output similar to this:
{
"mcpServers": {
"laravel-forge-mcp-server": {
"command": "npx",
"args": [
"path/to/your/laravel-forge-mcp-server/build/bin.js"
],
"env": {
"FORGE_API_KEY": "<REPLACE>",
"FORGE_SERVER_ID": "<REPLACE>",
"FORGE_SITE_ID": "<REPLACE>"
}
}
}
}Register an account at Laravel Forge
Related MCP server: forge-mcp-server
Sharing
If you have found value in this service please share it on social media. You can tag me @jordandalton on X, or jdcarnivore on Reddit.
Available Tools
1 tooldeploy-siteD
| Name | Required | Description | Default |
|---|---|---|---|
| deploy | Yes | Deploy the site. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'deploy-site' has a distinct purpose by default.
A single tool inherently has perfect naming consistency since there are no other tools to compare against. The name 'deploy-site' follows a clear verb-noun pattern.
One tool is too few for a server named 'Laravel Forge MCP Server', which suggests a domain (Laravel Forge server management) that typically requires multiple operations like managing sites, servers, deployments, and configurations. A single deployment tool feels incomplete for this scope.
The tool set is severely incomplete for Laravel Forge management. It lacks essential operations such as creating sites, listing servers, managing environment variables, or handling SSL certificates, leaving major gaps that will cause agent failures in typical workflows.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Create, deploy, and operate MCP servers directly from your GitHub repositories.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceIntegrates with the Laravel Forge API to provide comprehensive management of servers and sites. It enables users to perform health checks, monitor logs, create resources, and execute deployment tasks through MCP-compliant tools.292MIT
- AlicenseBqualityDmaintenanceMCP server for managing Laravel Forge servers, sites, and deployments via the Forge API.121,2378MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that connects to a Laravel Tasks API, enabling AI assistants to perform CRUD operations on tasks.
- AlicenseAqualityBmaintenanceA read-only MCP server for the Laravel Forge API, enabling AI assistants to query Forge infrastructure details like servers, sites, deployments, and logs without any write capabilities.2019MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/JordanDalton/laravel-forge-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server