Bring Carbon Offsetting
to LangChain
Learn how to connect Cloverly to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Cloverly through native MCP adapters. Connect 12 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Cloverly MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Cloverly queries for multi-turn workflows
Cloverly in LangChain
Cloverly and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Cloverly to LangChain 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 LangChain
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 LangChain 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 LangChain
Every tool call from LangChain 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 LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters