Bring Carbon Emissions
to Cursor
Learn how to connect SkootEco to Cursor and start using 18 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the SkootEco MCP Server?
Take control of your corporate sustainability targets by connecting SkootEco to your AI agents. With 18 specialized environmental tools, your AI can programmatically log emissions across all GHG scopes, purchase certified carbon offsets, track reforestation projects, and dynamically generate compliance reports.
What you can do
- Track direct and indirect emissions (GHG Scope 1, 2, 3)
- Automatically calculate supply chain carbon footprint
- Purchase certified carbon offset credits programmatically
- Fund reforestation projects and track your tree count
- Publish your public sustainability impact profile
- Generate CSRD and TCFD-aligned ESG reports
How it works
1. Subscribe to this server 2. Enter your SkootEco API Key (found in your provider dashboard) 3. Let your AI seamlessly manage your carbon compliance directly via VinkiusWho is it for?
Crucial for ESG managers, sustainability officers, and environmentally conscious businesses looking to accurately track, offset, and report on their carbon emissions.Built-in capabilities (18)
Log an emission
Verify connectivity
Get account info
Get total emissions
Get emissions by category
Get emissions by scope
Get ESG report
Get impact profile
Get impact metrics
Get offset details
Get project details
Get summary report
Get tree count
List emission categories
List carbon offsets
List climate projects
Plant a tree
Purchase carbon offset
Why Cursor?
Cursor's Agent mode turns SkootEco into an in-editor superpower. Ask Cursor to generate code using live data from SkootEco and it fetches, processes, and writes. all in a single agentic loop. 18 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
SkootEco in Cursor
SkootEco and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect SkootEco to Cursor 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 SkootEco in Cursor
The SkootEco 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 18 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor 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
SkootEco for Cursor
Every tool call from Cursor to the SkootEco MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can my AI retrieve a breakdown of our emissions by scope?
Simply use the get_emissions_by_scope tool. Your agent will instantly fetch data categorized by GHG Scope 1 (direct emissions), Scope 2 (energy), or Scope 3 (supply chain), perfectly aligned with the GHG Protocol.
Is it possible to automatically fund reforestation projects?
Yes. By executing the plant_trees action, your AI agent can programmatically fund tree planting projects to offset emissions, and return the updated total tree count in real time.
Can I automatically generate ESG compliance reports for stakeholders?
Absolutely. Ask the agent to use the generate_esg_report tool. It will compile your sustainability data into compliance reports aligned with CSRD and TCFD frameworks, ready for your next board meeting.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.