Greenspark Impact API (MCP reads)
Related skills
Apply greenspark-mcp and greenspark-auth-environments before live calls.
- Domain reference: https://docs.getgreenspark.com/reference/impacts
Ledger endpoints (MCP when toggled)
| operationId | Route |
|-------------|-------|
| getImpactPurchases | GET /impacts/purchases |
| getImpactPurchase | GET /impacts/purchases/:purchaseId |
Use get-endpoint for schema, then optional execute-request on GET with a sandbox key.
Impact creation (POST) is documented on ReadMe but not executable via MCP v1 — implement writes in your application and use the API docs for POST schemas.
MCP rules (v1)
- Impact spec is MCP-enabled for GET ledger routes when toggled in ReadMe.
- Read-only via MCP in v1.
Agent guidance
- For ledger or purchase history: use
getImpactPurchasesorgetImpactPurchase. - Prefer sandbox for exploratory reads.