How to Use the Greenspark MCP in Cursor

Q: How do I add the Greenspark MCP Server to my Cursor editor?

Add the Greenspark configuration block to your .cursor/mcp.json file in your project root. Cursor will automatically detect the server and make the tools available in Agent mode.

Q: Can Cursor test Greenspark webhooks locally?

Yes. Cursor uses createwebhook to register local tunnel URLs during development. This lets you test how your application handles Greenspark impact payloads before deploying.

Q: Can I list active Greenspark badges inside Cursor?

Yes. Cursor uses listbadges to pull the SVG code or URLs for your impact widgets. The agent can then write the exact HTML or React components to display these badges on your site.

Q: What data does Greenspark access when running inside Cursor?

Only the specific parameters sent to estimatefootprint or createimpact leave your machine. Your proprietary codebase and local repository files are never uploaded, keeping your intellectual property secure within Cursor's local sandbox.

Build automated climate actions directly into your codebase with Cursor and Greenspark.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Greenspark MCP to Cursor

Create your Vinkius account to connect Greenspark to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Greenspark with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Generate climate-positive code in Cursor Agent mode

The `create_impact` tool lets your Cursor agent write and test actual climate actions directly inside your active codebase. When you run your test suites, the Cursor agent can trigger real-world Greenspark offsets to verify your integration works before you push to production. This MCP Server connection allows Cursor to write the exact Greenspark API calls you need. Cursor reads your live configuration using `get_subscription` to write precise, functional code that matches your actual Greenspark tier.

Embed footprint calculators into your Cursor workspace

Analyzing your database schemas to estimate their carbon footprint is simple inside Cursor with the `estimate_footprint` tool. The Cursor editor reads your data structures and writes Greenspark functions that calculate emissions on the fly. Instead of guessing your environmental impact, this MCP integration gives Cursor the live Greenspark data it needs to build accurate calculator modules. The Cursor agent uses `list_impact_types` to align your code with real-world Greenspark carbon offset standards.

Configure webhooks directly from the Cursor terminal

Configuring and registering webhooks for your Greenspark climate events happens directly in your Cursor editor with the `create_webhook` tool. Your Cursor agent can write the endpoint code, deploy it, and register it with Greenspark in one continuous flow. Cursor uses `list_webhooks` to audit your active endpoints and ensure your production environment receives Greenspark impact updates. It eliminates the back-and-forth of manual API testing by keeping your Greenspark webhook management inside the Cursor editor.

Setup guide

Set up Greenspark MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Greenspark MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Greenspark transactions." If the MCP tools are loaded correctly, Cursor will call the Greenspark tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "greenspark-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Greenspark. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Greenspark now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Greenspark MCP in Cursor

Add the Greenspark configuration block to your `.cursor/mcp.json` file in your project root. Cursor will automatically detect the server and make the tools available in Agent mode.

Yes. Cursor uses `create_webhook` to register local tunnel URLs during development. This lets you test how your application handles Greenspark impact payloads before deploying.

Cursor accesses your API token through your environment variables or local MCP settings. It uses `get_subscription` to verify your credentials without exposing your private keys in your codebase.

Yes. Cursor uses `list_badges` to pull the SVG code or URLs for your impact widgets. The agent can then write the exact HTML or React components to display these badges on your site.

Only the specific parameters sent to `estimate_footprint` or `create_impact` leave your machine. Your proprietary codebase and local repository files are never uploaded, keeping your intellectual property secure within Cursor's local sandbox.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript