Laravel Cloud MCP integration for AI agents.
Connect AI agents to Laravel Cloud through 8 structured actions, including get application, get deployment, and get environment. Review authentication, input…
- ACTION CONTRACTS
- 8
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Laravel Cloud integration exposes
The Laravel Cloud Agent App exposes 8 provider-backed actions for developer tools and storage work. Its current contract lets an authorized agent get a specific laravel cloud application, get a specific laravel cloud deployment, and get a specific laravel cloud environment. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Laravel Cloud account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Laravel Cloud capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_applicationREADGet a specific Laravel Cloud application.
INPUTS: applicationId / include
get_deploymentREADGet a specific Laravel Cloud deployment.
INPUTS: deploymentId / include
get_environmentREADGet a specific Laravel Cloud environment.
INPUTS: environmentId / include
get_organizationREADGet the Laravel Cloud organization associated with the API token.
list_applicationsREADList Laravel Cloud applications for the authenticated organization.
INPUTS: name / region / slug / include
list_deploymentsREADList Laravel Cloud deployments for an environment.
INPUTS: environmentId / status / branchName / commitHash / include
list_environmentsREADList Laravel Cloud environments for an application.
INPUTS: applicationId / name / status / slug / include
list_regionsREADList cloud regions currently available in Laravel Cloud.
INPUT CONTRACTS
Know what the action needs before it runs.
get_application
applicationIdREQUIRED- The Laravel Cloud application identifier.
includeOPTIONAL- Related application resources to include.
get_deployment
deploymentIdREQUIRED- The Laravel Cloud deployment identifier.
includeOPTIONAL- Related deployment resources to include.
get_environment
environmentIdREQUIRED- The Laravel Cloud environment identifier.
includeOPTIONAL- Related environment resources to include.
list_applications
nameOPTIONAL- Filter applications by name.
regionOPTIONAL- Filter applications by region identifier.
slugOPTIONAL- Filter applications by slug.
includeOPTIONAL- Related application resources to include.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Application
Get a specific Laravel Cloud application. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_applicationVerify with Get Deployment
Get a specific Laravel Cloud deployment. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_deploymentSAFETY BOUNDARY
Operate Laravel Cloud with explicit limits
- Authorize Laravel Cloud with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Laravel Cloud data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Laravel Cloud rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Laravel Cloud task completed successfully.
CONNECTION MODEL
API key
Laravel Cloud API token used with the Authorization: Bearer header. Create it from your Laravel Cloud organization settings under API tokens: https://cloud.laravel.com/docs/api/authentication
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Laravel Cloud.