How do I get started?

Subscribe, copy your active API Token (which you generate inside **Forge Dashboard → API**), and connect it. The integration expects standard connections so you can trigger real build routines natively without intricate pipelines or ssh logic.

Can my AI automatically trigger site deployments?

Yes! Give the agent the Server ID and Site ID you're questioning. It utilizes `deploy_site` to physically POST to Forge's pipelines kicking off an automated release. Perfect for hands-free releases right from Cursor.

What happens when I want to fetch metrics on queued application workers?

Provide the exact IDs. The tool evaluates endpoint rules (`list_workers`) and unpacks default configurations running PHP queues natively back to the terminal screen.

Does it list physical server setups efficiently?

Absolutely. Execute 'list_servers' or probe 'list_ssh_keys'. It aggregates root connection statuses, IPs, and structural records giving immense monitoring peace-of-mind at the keyboard.

Laravel Forge MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: Laravel Forge
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to Laravel Forge through Vinkius, pass the Edge URL in the `mcps` parameter and every Laravel Forge tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Laravel Forge Specialist",
    goal="Help users interact with Laravel Forge effectively",
    backstory=(
        "You are an expert at leveraging Laravel Forge tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Laravel Forge "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Laravel Forge MCP Server

Connect your Laravel Forge developer account to an AI agent to execute complex devops tasks natively in chat.

When paired with CrewAI, Laravel Forge becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Laravel Forge tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Server Ecosystems — List all connected drops, inspect internal structures, and check status
Deployments — Safely dispatch site deployment scripts and watch output structures
Database Configurations — Query connected DB clusters linked to given domains
Worker Operations — Expose active daemon configurations routing jobs under your servers

The Laravel Forge MCP Server exposes 9 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Laravel Forge to CrewAI via MCP

Follow these steps to integrate the Laravel Forge MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 9 tools from Laravel Forge

Why Use CrewAI with the Laravel Forge MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Laravel Forge through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Laravel Forge + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Laravel Forge MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Laravel Forge for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Laravel Forge, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Laravel Forge tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Laravel Forge against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Laravel Forge MCP Tools for CrewAI (9)

These 9 tools become available when you connect Laravel Forge to CrewAI via MCP:

deploy_site

Command a deployment script queue to execute on a repository site

get_server

Retrieve detailed data on a specific server droplet

get_site

Look up specifics for an exact site layout on a server

list_databases

List active databases mounted on a Forge server

list_recipes

Retrieve available custom shell recipes within your organizational team limits

list_servers

Retrieve the master list of all connected Forge servers

list_sites

List websites mounted to a specific server

list_ssh_keys

Retrieve active physical access keys inserted on the root server

list_workers

Retrieve queue worker configurations executing on a tracked site

Example Prompts for Laravel Forge in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Laravel Forge immediately.

"Display all the cloud server instances operating in the fleet."

"Deploy the pending commits directly to staging site 5210 on server 1205."

"Check the active workers running on the production server."

Troubleshooting Laravel Forge MCP Server with CrewAI

Common issues when connecting Laravel Forge to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Laravel Forge + CrewAI FAQ

Common questions about integrating Laravel Forge MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.