Bring Albi
to CrewAI
Learn how to connect Albi Restoration to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Albi Restoration MCP Server?
Connect your Albi (albiware.com) account to any AI agent and take full control of your restoration contracting and project management workflows through natural conversation.
What you can do
- Project Lifecycle Orchestration — List and manage all restoration projects programmatically, retrieving detailed high-fidelity statuses, staff assignments, and timelines in real-time
- Financial Insights & KPIs — Programmatically retrieve project-specific financial data, including high-fidelity revenue metrics, costs, and gross margins directly through your agent
- Relationship Management Architecture — Access and manage your entire database of individual contacts, clients, and business organizations to maintain a perfectly coordinated ecosystem
- Inventory & Asset Tracking — Programmatically track physical equipment and specialized restoration gear to oversee your organization's assets and availability efficiently
- Operational Monitoring — Access project activities, monitor active webhooks, and verify API connectivity directly through your agent for instant reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Albi settings (Settings > Integrations)
3. Start orchestrating your restoration business from Claude, Cursor, or any MCP client
No more manual logging into field service apps or digging through complex financial spreadsheets. Your AI acts as your dedicated project coordinator and business analyst.
Who is this for?
- Restoration Contractors — instantly retrieve project summaries and update statuses using natural language commands
- Project Managers — monitor staff assignments and track financial KPIs across multiple sites without leaving your workspace
- Operations Leads — automate the oversight of organization-wide inventory and contact directories through simple AI queries
Built-in capabilities (12)
Verify Albi API status
Add a new contact
Requires project name and primary contact. Start a new project
Get details for a specific project
Retrieve financial KPIs for a project
List active webhooks
List available project roles
List assets and equipment
List all tasks and activities
List all contacts
List all organizations
List all restoration projects
Why CrewAI?
When paired with CrewAI, Albi Restoration becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Albi Restoration tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
Albi Restoration in CrewAI
Albi Restoration and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Albi Restoration to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Albi Restoration in CrewAI
The Albi Restoration 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. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Albi Restoration for CrewAI
Every tool call from CrewAI to the Albi Restoration MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Albi API Key?
Log in to your account, navigate to Settings > Integrations, and click the 'API Key' button to generate or copy your unique token.
Can I track financial KPIs via AI?
Yes! The get_project_financial_kpis tool allows your agent to retrieve high-fidelity revenue, cost, and margin data for any specific project ID.
How do I check available inventory?
Use the list_inventory_equipment tool to retrieve a complete high-fidelity list of all physical assets and specialized gear managed in your account.
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.
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.