Laravel Forge MCP Server
Related Servers
Alternatives to Laravel Forge MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server enabling AI assistants to manage Laravel Forge through the full Forge API v2, with ~270 tools for servers, sites, deployments, databases, backups, and more.23 npmMIT
- AlicenseBqualityDmaintenanceMCP server for managing Laravel Forge servers, sites, and deployments via the Forge API.121,188 npm8MIT
- AlicenseAqualityCmaintenanceMCP server exposing the Laravel Forge API v2 with curated tools for deploys, logs, env, and services plus universal access to all 273 operations.28Apache 2.0
- 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.203 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server that connects to a Laravel Tasks API, enabling AI assistants to perform CRUD operations on tasks.-
- 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.29 npm2MIT
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.