A
licenseNot graded
qualityB
maintenanceMCP 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.
20 npm
MIT
laravel-forge-readonly-mcp
Related Servers
Alternatives to laravel-forge-readonly-mcp
No user-submitted related servers found.
Related Servers
- AlicenseDqualityDmaintenanceA 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.12MIT
- 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.32 npm2MIT
- 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
- AlicenseBqualityCmaintenanceMCP server for managing Laravel Forge servers, sites, and deployments via the Forge API.1283 npm9MIT
- AlicenseAqualityBmaintenanceRead-only MCP server for the RareCloud API, enabling AI agents to list servers, browse the catalog, check billing, and plan deployments.10025 npmMIT
TDQS
A3.9/5.0
Scored across 25 tools
Disambiguation4/5
Each named tool targets a distinct Forge resource or action, and the descriptions do a good job clarifying scope and required identifiers. However, the cluster of output/log readers (get_deployment_log, get_command_output, get_scheduled_job_output, get_server_event_output, get_background_process_log) and the forge_get catch-all can be mistaken for one another without reading the full descriptions.
Naming Consistency4/5
Nearly all tools follow a predictable snake_case verb_noun pattern (list_servers, get_site, list_deployments). The main deviations are forge_get's prefix order and a slight suffix inconsistency between *_output and *_log, but overall naming is readable and consistent.
Tool Count3/5
25 tools is borderline heavy for a read-only surface. The breadth of Laravel Forge justifies many tools, but several resource-specific readers (sites, deployments, logs, outputs) could be consolidated, especially since forge_get already covers uncovered endpoints.
Completeness4/5
The surface provides strong read-only coverage for servers, sites, deployments, databases, backups, scheduled jobs, logs, certificates and integrations. Minor gaps for first-class tools covering monitors, firewall rules, Nginx templates, teams and similar areas are workable via forge_get, and a few log tools may return 403 with a strictly read-only token.
Maintenance
ActivityMaintained
ResponsivenessNo issues