Skip to content
← Directory

mcp · Global

carbon-compass

Full-stack SAP capstone: ABAP RAP + CDS + Fiori Elements on BTP, with an MCP server exposing ESG emissions data to an LLM copilot.

Feature or claim this listing

Feature this listing — founding Featured slots are 50% off for 6 months

Represent carbon-compass? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Explore paid sponsorship →

What's in it

Data offered docs-verified
GHG emissions records per facility, reporting period and scope (SCOPE1, SCOPE2, SCOPE3) · Line items per activity type with quantity, unit and CO2e · CO2e calculated as quantity × emission factor, summed to record total · Emission factors by activity type · Facilities
Resolution llm-inferred
Record level: facility × reporting period (e.g. 2025-Q1) × scope; no finer spatial resolution is documented
Formats docs-verified
MCP stdio · OData V4 · JSON (HTTP bridge) · PDF (print from HTML report)
Access docs-verified
SAP BTP ABAP Environment (trial) system with Basic auth credentials via ODATA_USERNAME / ODATA_PASSWORD; docs state Basic auth, catalogue metadata says API key; licence not stated

Useful for

Use cases llm-inferred
Draft a Scope 1-3 emissions register for a client's sites by reporting period · Pull per-facility CO2e totals and emission factors for ESG reporting packs · Generate print-ready emissions summary PDFs for a site portfolio review
Audience llm-inferred
ESG and sustainability consultants · environmental consultants · SAP BTP / ABAP developers · GIS and data analysts

Limitations

Constraints llm-inferred
If the SAP call fails (no credentials, 401, timeout), the MCP tools return built-in sample data that is independent of the connected system · Coverage depends entirely on what facilities, records and emission factors are loaded; docs give no geographic or time span · Emission factor source and authority are not documented; factors are user-maintained in ZESG_EMFACTOR · Requires an SAP BTP ABAP trial system and a local Node.js install with Claude Desktop configuration · Capstone project; maintenance and support commitments are not documented · Docs list a 'Known gaps and roadmap' section that was not included in the supplied text
Licence
Unknown — check provider terms
Authentication
API key via env: ODATA_PASSWORD, ODATA_USERNAME (auto-extracted from README)
GitHub stars
1
Last commit
03/10/2026
Last successful page check
14/10/2026
Page health
healthy
Package
Not recorded
Verification
Not independently verified

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Provenance & evidence

Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).

Metadata observed 16/10/2026 · research sweep: github-search