forge-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORGE_API_KEY | Yes | Your Laravel Forge API key |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_serversA | List all Laravel Forge servers |
| get_serverB | Get details of a specific server |
| list_sitesB | List all sites on a server |
| get_siteB | Get details of a specific site |
| deploy_siteC | Deploy a site |
| get_deploymentsC | Get deployment history for a site |
| get_deployment_scriptB | Get the deployment script for a site |
| update_deployment_scriptC | Update the deployment script for a site |
| toggle_quick_deployC | Enable or disable quick deploy for a site |
| reboot_serverD | Reboot a server |
| get_server_loadC | Get server load metrics |
| reset_deployment_stateC | Reset deployment state for a site |
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 12 tools
Each tool targets a distinct action and resource (site, server, deployment). No two tools have overlapping purposes; descriptions are clear and unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., deploy_site, get_server_load). No deviation or mixing of conventions.
12 tools is well-scoped for a server management API. Each tool earns its place, covering server and site details, deployment operations, and script management without being overwhelming.
Core monitoring and deployment operations are present, but basic lifecycle actions like creating or deleting servers/sites are missing, representing notable gaps for full CRUD coverage.