Laravel Forge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deploy-siteD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.