Laravel Forge MCP Server
# Laravel Forge MCP Server
> Mininum build to solve just one problem.
To build the MCP server, run:
```
npm install && npm run build
```
This 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:
```json
{
"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](https://forge.laravel.com/)
## Sharing
If you have found value in this service please share it on social media. You can tag me [@jordandalton](https://x.com/jordankdalton) on X, or [jdcarnivore](https://www.reddit.com/user/jdcarnivore) on Reddit.TDQS
Scored across 1 tool
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.