Greenspark
About
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.
Details
- Author
- Unknown
- Categories
- Marketing, API, Automation
Jump to
Fetch the complete documentation index at:https://docs.getgreenspark.com/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version.
The GreensparkModel Context Protocol (MCP)server lets AI editors (Cursor, Windsurf, VS Code) and tools like Claude Desktop work withGreenspark API documentationand, where enabled,read-only live API callsagainst your account.
- API reference access— list and inspect endpoints, parameters, and response schemas
- Documentation context— Greenspark OpenAPI specs and guides
- Read-only live calls (v1)—execute-requeston enabledGETroutes when you provide a valid API key
- Integration help— schema-aware answers and example requests for building against Greenspark
v1 limits:MCP isread-only. POST, PUT, PATCH, and DELETE routes are documented for building integrations; useget-endpointfor schemas, notexecute-requestfor writes. Billing, Email, and Estimations arenotexposed via MCP route toggles in v1.
- A Greenspark account with an API key (create keys in the dashboard after registration).
- Match key to host:sandbox key →https://sandbox.getgreenspark.com; production key →https://api.getgreenspark.com.
- For first tests, use asandboxkey.
Authentication uses thex-api-keyheader on live API calls. Some MCP clients let you attach headers to the MCP server config; otherwise the agent passes the key when callingexecute-request.
No MCP password is required for v1 (leave blank in ReadMe MCP settings).
json { "mcpServers": { "greenspark": { "url": "https://docs.getgreenspark.com/mcp", "headers": { "x-api-key": "YOUR_SANDBOX_OR_PRODUCTION_API_KEY" } } } } ` Restart Cursor after saving. Prefer a sandbox key while testing.
json { "mcpServers": { "greenspark": { "url": "https://docs.getgreenspark.com/mcp", "headers": { "x-api-key": "YOUR_SANDBOX_OR_PRODUCTION_API_KEY" } } } } json { "mcpServers": { "greenspark": { "url": "https://docs.getgreenspark.com/mcp", "headers": { "x-api-key": "YOUR_SANDBOX_OR_PRODUCTION_API_KEY" } } } } json { "mcpServers": { "greenspark": { "url": "https://docs.getgreenspark.com/mcp", "headers": { "x-api-key": "YOUR_SANDBOX_OR_PRODUCTION_API_KEY" } } } } Note:If your client does not support headers on the MCP URL, connect without them and supplyx-api-keywhen the agent runsexecute-requestagainst Greenspark hosts.
Specs with MCP exposure in v1:Impact, Reporting, Account, Projects.
Not executable via MCP v1 toggles:Estimations, Email, Billing (docs only).
Some routes require specificsubscription plansor key types; failed calls may return401,403, or422(API quota exhausted).
The MCPserverruns on ReadMe athttps://docs.getgreenspark.com/mcp. For editor configs, Agent Skills, and registry metadata, use the public GitHub repo:
Skills areoptional. They help agents use Greenspark MCP correctly (auth, environments, and domain GET workflows). They do not replace live schemas fromget-endpointon this docs site.
npx skills add getgreenspark/mcp -a cursor -g -y ## Testing your setup 1. Connect your editor to https://docs.getgreenspark.com/mcp (with sandbox x-api-key if supported). 2. Open a new agent chat and confirm the Greenspark MCP tools are listed. 3. Try read-only prompts, for example: "List Greenspark MCP endpoints for Account." "Show the schema for GET public account v2." * "Using my sandbox key, call GET /v2/account/ with my account ID" (only if that route is enabled in ReadMe). 4. Confirm write operations are not run via MCP — ask for a POST example as code in your app instead. For machine-readable docs without MCP, see https://docs.getgreenspark.com/llms.txt.
Free MCP that drives an audit of your marketing. Your AI connects, adsOS digs through your ads, email and site, and hands back a growth plan you can run today.
Apigene MCP Gateway is the runtime layer that connects AI agents to APIs and MCP servers via Model Context Protocol.
The MCP server for Bitrix24 provides AI assistants with structured access to the Bitrix24 API. It delivers up-to-date method descriptions, parameters, and valid values, allowing assistants to work with precise data instead of guesswork. This reduces code errors and accelerates Bitrix24 integration development.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Interact with any other SaaS applications on behalf of your customers.
One MCP server for AI agents to use any tools reliably at any scale
Magica is your all-in-one AI platform, offering 2500+ cutting-edge tools under a single subscription.
Turn your Make scenarios into callable tools for AI assistants.
One remote MCP server for 500+ production APIs — Stripe, HubSpot, Postgres, Gmail, and more. OAuth and API key auth, credential management, and a CLI.
One API key, dozens of capabilities for your AI agent. Zero provider auth.
Hosted remote MCP server with managed OAuth for a growing list of 15+ toolkits, including Google Workspace, Last.fm, MusicBrainz, Fitbit, Oura, Kalshi, and Polymarket.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
