Bring Carbon Offsetting
to CrewAI
Learn how to connect Cloverly 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 Cloverly MCP Server?
Connect your Cloverly account to any AI agent and take full control of your sustainability initiatives and automated carbon management workflows through natural conversation.
What you can do
- Footprint Orchestration — Calculate real-time carbon footprint estimates for diverse activities including logistics (freight, shipping), travel (flights, vehicles), and energy usage programmatically
- Automated Offset Ingestion — Execute the purchase of carbon offsets based on specific activity estimates or fixed currency amounts to maintain high-fidelity sustainability compliance
- Project Intelligence — Access your complete directory of high-impact environmental projects (wind, solar, reforestation) to understand the source of your offsets directly through your agent
- Transaction Monitoring — Programmatically track your purchase history and retrieve detailed metadata, certificates, and receipts for operational and regulatory reporting
- Sustainability Visibility — Check the status of individual offset purchases and monitor account-level metadata to perfectly coordinate your organization's climate action
How it works
1. Subscribe to this server
2. Retrieve your Public and Private API Keys from the Cloverly dashboard (Settings > API)
3. Start offsetting your business operations from Claude, Cursor, or any MCP client
No more manual footprint spreadsheets or searching for carbon certificates in the portal. Your AI acts as your dedicated sustainability engineer and climate coordinator.
Who is this for?
- Sustainability Managers — instantly calculate project footprints and manage offset portfolios using natural language commands
- Logistics & E-commerce Ops — automate carbon offsetting for every shipment and monitor environmental impact without leaving your workspace
- Growth Engineers — integrate real-time carbon calculation and purchase features into custom internal tools through simple AI queries
Built-in capabilities (12)
Verify connectivity
Create a carbon estimate
Purchase carbon offsets
Get account info
Get estimate details
Get impact by type
Get impact summary
Get project details
Get purchase details
List estimates
List offset projects
List purchases
Why CrewAI?
When paired with CrewAI, Cloverly becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Cloverly 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
Cloverly in CrewAI
Cloverly and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Cloverly 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 Cloverly in CrewAI
The Cloverly 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
Cloverly for CrewAI
Every tool call from CrewAI to the Cloverly 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 Cloverly API Keys?
Log in to your account, navigate to Settings > API, and you will find your Public and Private keys for both Production and Sandbox environments.
Can I calculate carbon for shipping packages?
Yes! The create_estimate tool allows you to provide weight and distance parameters to get an accurate carbon footprint for logistics.
How do I retrieve a carbon certificate?
After a successful purchase, use the get_purchase_status tool to retrieve the unique certificate and receipt URL for your record.
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.