Greenspark
Greenspark MCP lets AI builders and agents easily add verified climate actions, such as planting trees, recovering ocean-bound plastic, protecting bees, restoring kelp, offsetting carbon, and funding clean water, directly into their products and workflows.
⌁ labsco summary — our analysis, not the vendor's
What it is — An MCP server (hosted by ReadMe) that lets AI editors and Claude Desktop work with Greenspark's API docs and, where enabled, make read-only live GET calls to add verified climate actions.
What you get
- Browse API reference — e.g. "list Greenspark's Impact endpoints and their schemas".
- Search endpoints by keyword — e.g. "find the route for planting trees".
- Read-only live GET calls (v1) — e.g. "execute a GET on an enabled Projects route with my API key".
- Schema-aware integration help for building against Greenspark v1.
Requirements — Greenspark account with an API key (x-api-key header); match key to host (sandbox vs production). MCP is read-only in v1 — no writes; Billing/Email/Estimations not exposed.
Cost snapshot — Pricing not published on the provided page.
Setup effort — Add https://docs.getgreenspark.com/mcp with your x-api-key to your client (e.g. ~/.cursor/mcp.json), preferring a sandbox key while testing.
Our take — Handy for developers integrating climate actions (tree planting, ocean plastic, carbon offset) who want doc-grounded, schema-aware help; MCP is read-only, so you build write integrations against the API itself, not through MCP.
Sources: https://docs.getgreenspark.com/docs/mcp — verified 2026-07-08.
Greenspark MCP lets AI builders and agents easily add verified climate actions, such as planting trees, recovering ocean-bound plastic, protecting bees,...
Add to ~/.cursor/mcp.json: {"mcpServers":{"greenspark":{"url":"https://docs.getgreenspark.com/mcp","headers":{"x-api-key":"YOUR_SANDBOX_OR_PRODUCTION_API_KEY"}}}}No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.