A
licenseB
qualityD
maintenanceMCP server for managing Laravel Forge servers, sites, and deployments via the Forge API.
12
1,188 npm
8
MIT
laravel-forge-mcp
by wdevcom
Related Servers
Alternatives to laravel-forge-mcp
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
- 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
- FlicenseDqualityDmaintenanceA minimalist MCP server that integrates with Laravel Forge, allowing users to manage their Laravel Forge servers, sites, and deployments through AI assistants like Claude Desktop, Windsurf, or Cursor.12-
- 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
- FlicenseBqualityDmaintenanceMCP server for Laravel Cloud to manage projects, environments, deployments, and other resources.98-
TDQS
A3.8/5.0
Scored across 28 tools
Disambiguation5/5
Each tool targets a distinct resource/action: list/get/update/deploy/status are separated, and logs are explicitly scoped to server, site, or deployment. The generic forge_search_operations/forge_call pair is clearly framed as a fallback for operations without a dedicated tool, so it does not create ambiguity.
Naming Consistency4/5
The forge_ prefix and snake_case are consistent, and most names follow verb_noun patterns like forge_list_servers, forge_get_site, and forge_update_env. A few names deviate with noun-phrase or verb-only forms such as forge_deployment_status, forge_server_events, forge_background_process_action, forge_resolve, and forge_call, so the pattern is mostly but not perfectly uniform.
Tool Count3/5
28 tools is on the heavy side and above the ideal discoverability range for an MCP server. However, the Laravel Forge domain is broad and the tools are grouped by server, site, deployment, background process, and database concerns, so the set is not redundant; the generic forge_call/search pair also keeps the count from needing to grow further.
Completeness5/5
The dedicated tools cover core server, site, deployment, env, nginx, background process, scheduled job, and database workflows. Because forge_search_operations and forge_call expose all 273 Forge API operations, any missing capability such as certificates, firewall rules, recipes, or backups remains reachable without a dead end.
Maintenance
ActivitySlowing
ResponsivenessNo issues