🌱 Eco-Loom: A Sustainability Operations Workspace

This is a submission for the Notion MCP Challenge

What I Built

I built Eco-Loom, a multi-facility sustainability operations workspace that helps teams track carbon emissions without drowning in spreadsheets, scattered documents, and disconnected reporting tools.

The idea came from a simple frustration:

carbon accounting is often treated like a reporting exercise at the end of the month—when it should feel like an operational system teams can use every day.

Eco-Loom turns that process into a live workflow.

Teams can:

• Capture emissions data
• Manage a carbon ledger
• Compare facilities and sites
• Monitor monthly trends
• Track sustainability goals
• Review gap analysis
• Generate report-ready outputs

All from a single workspace.

The product is designed around visibility and action.

Instead of asking:

“Where did this number come from?”

“Which site is off track?”

Eco-Loom makes those answers visible immediately.

---

🎥 Video Demo

Try it yourself:

👉 Live Demo Link

Demo Login Credentials:

• Email: [e-mail]
• Password: eco-loom-local-admin

Video walkthrough:

In the demo, I show how a team can:

• Log into Eco-Loom and land in a facility-aware sustainability dashboard
• Switch between sites to see how emissions, trends, and goal health change
• Review emissions by category, gap analysis, and recent activity
• Manage carbon-ledger records and see how data feeds reporting workflows
• Generate reports with facility context included
• Use the Notion-connected workflow as a collaboration and review layer

---

💻 Show Us the Code

A key part of the implementation is the company-scoped Notion configuration layer.

Since Eco-Loom is multi-workspace and multi-facility, Notion cannot be treated as a single global integration.

export async function getCompanyNotionConfig(
  companyId: string,
  options: CompanyNotionConfigOptions = {}
) {
  const { createIfMissing = false, adoptLegacy = true } = options;

  const companyConfig = await db.notionConfig.findUnique({
    where: { companyId },
  });

  if (companyConfig) {
    return ensureEncryptedNotionApiKey(companyConfig);
  }

  if (createIfMissing) {
    return db.notionConfig.upsert({
      where: { companyId },
      update: {},
      create: {
        companyId,
        syncEnabled: true,
      },
    });
  }

  return null;
}

That small layer matters because it:

• Keeps each workspace isolated
• Makes Notion sync safer
• Supports a more production-ready sustainability workflow

---

🔗 How I Used Notion MCP

Notion MCP is one of the most important parts of Eco-Loom.

I used it to connect Eco-Loom with structured Notion databases for:

• Carbon Ledger
• Sustainability Goals
• Reports
• Facilities / Sites
• Operations follow-up

This means Notion is not just a note-taking add-on—it becomes the collaboration layer around the product.

With MCP, Eco-Loom can:

• Sync records into Notion
• Preserve workspace context
• Power a custom sustainability operations agent that:
  • Reviews data quality
  • Flags missing fields
  • Detects duplicate risks
  • Prepares monthly follow-ups

---

⚙️ What This Unlocks

This creates a much stronger workflow:

• Eco-Loom → structured sustainability system of record
• Notion → human collaboration and review environment
• MCP → bridge connecting data, workflows, and reporting

All together, they form a closed operational loop.

---

🚀 Final Thoughts

In short, Notion MCP helped turn Eco-Loom from a dashboard into a true sustainability operating system.