Skip to main content
Orki MCP • LCA • FDES • PEP • EN 15804

Your life cycle assessments, queried from your AI assistant

  • Results you can read: impacts by stage, by component and by indicator, explained in plain language from Orki's calculations.
  • Checks before verification: pre-audit, inventory consistency and preparation of the INIES export, before handing over to the verifier.
  • Source data at hand: flat inventory and ecoinvent or INIES emission factors, to understand where each figure comes from.

See the platform in action

An Orki expert will get in touch to arrange your demo.

OK

Request sent!

We have received your request. Our team will be in touch very shortly.

How did you hear about us?

📢 Advertising
🔍 Google
💼 LinkedIn
💬 Word of mouth
🤖 ChatGPT or another AI
❓ Other
Error

Something went wrong

Please try again later or email us directly at contact@orki.green.

Your AI assistantOrki connector enabled

Summarise the LCA of our radiator: climate change impact by stage, and the three components that weigh the most.

Orki · LCA results by stageOrki · LCA inventory

Climate change, 186 kgCO2e per radiator over the life cycle:

StagekgCO2eShare
Manufacturing (A1 to A3)13271%
Use (B6)4122%
End of life (C1 to C4)137%

The three components that weigh the most: the steel body (48%), the heating element (17%) and the cardboard packaging (6%). Would you like the breakdown by EN 15804 indicator?

Fictitious conversation, sample data. The results are calculated by the platform; the assistant only presents them.

In practice

LCA, in conversation

Requests that an assistant connected to your Orki LCAs can handle (fictitious data).

You

Summarise the LCA of our radiator: climate change impact by stage, and the three components that weigh the most.

Your assistant, via Orki

186 kgCO2e per unit over the life cycle: manufacturing 71%, use 22%, end of life 7%. The three heaviest components: the steel body (48%), the heating element (17%) and the cardboard packaging (6%).

You

Run the pre-audit of the FDES and list the blocking issues before sending it to the verifier.

Your assistant, via Orki

3 blocking issues: end-of-life scenario without a source, reference service life not justified, transport to the building site missing for 2 components. Plus 5 non-blocking remarks, including 2 factors more than 10 years old.

You

Compare the two variants of our packaging on the EN 15804 indicators.

Your assistant, via Orki

Variant B, in recycled cardboard, comes out ahead on 10 of the 13 indicators: -23% on climate change, -31% on fossil resource depletion. It loses on water use (+12%).

You

Find an ecoinvent factor for cold-rolled stainless steel.

Your assistant, via Orki

2 options in your version of ecoinvent: hot-rolled 18/8 chromium steel combined with the cold-rolling process, or a market dataset if one exists. I will give you the source and unit of each before assigning it.

The assistant's tools

What your assistant does in your LCAs

The assistant sees the LCAs in your workspaces within the limits of your LCA role. The calculation methods and checks are those of the platform.

Read

Your LCAs and their results, as calculated in Orki.

  • The list of your LCAs and their status
  • Results by stage and by indicator
  • The flat inventory, component by component

Check

The platform's deterministic checks, on demand.

  • The LCA pre-audit
  • Inventory consistency
  • Validation of the INIES export

Search

The data behind a result.

  • Emission factors from Orki's databases (ecoinvent, INIES...)
  • The details of a component and its factor

Understanding MCP

A standard connector between your AI and your Orki data

You don't need to be a developer to use it. Here is what it is, and what happens when your assistant works in Orki.

Youask your question in plain language
a conversation
Your AI assistantClaude, ChatGPT, Le Chat, Copilot...
the MCP protocol
The Orki platformyour data, your calculations, your permissions

What is MCP?

MCP (Model Context Protocol) is an open standard published by Anthropic in late 2024 and since adopted by most AI assistants. It defines a single way to connect an assistant to a piece of software.

It is often compared to a USB-C port: the same connection works whatever the assistant, and whatever the tool on the other side.

What difference does it make?

Without MCP, your assistant only knows what you paste into the conversation. With the Orki MCP, it reads your data on the platform, runs calculations, checks a file before import and, if you allow it, saves data.

You stay in the tool you already use, with the model you have chosen.

Who does the calculations?

Orki. The assistant never makes up an emission factor or a result: it calls the platform's tools, which apply the same rules and calculation methods as the application.

A result obtained through the assistant is therefore identical to the one you would read in Orki.

Security and control

Your assistant never has more permissions than you

The Orki MCP acts on behalf of the signed-in user, with exactly the permissions that user has in the application.

1

Sign-in with your Orki account

The assistant connects through OAuth, the standard for connections between applications. You sign in on Orki, never in the assistant, and no password is ever shared with it.

2

Your permissions, nothing more

Entities, roles, contributor restrictions, locked workspaces: anything you cannot do in the application, the assistant cannot do either. An auditor stays read-only.

3

The workspaces you choose

When you connect, you choose which workspaces the assistant can see. A workspace you have not ticked remains invisible to it.

4

Write access, on authorisation

Read access is granted by default; write access is turned off. You enable it workspace by workspace, and you can withdraw it whenever you like.

5

Revocable at any time

Connected applications are managed from Orki's settings: one click is enough to cut off an assistant's access.

6

No extra tokens to pay for

The model runs on your subscription to the assistant. Orki provides the data and the calculations, not the model.

Getting connected

Compatible with the main AI assistants

Claude, ChatGPT, Claude Code, Cursor, Mistral's Le Chat, Copilot in VS Code: any MCP-compatible assistant can connect to Orki. An Orki expert opens your access and sets up the connection with you, on your own workspaces.

ClaudeChatGPTClaude CodeCursorLe ChatCopilot

The Orki MCP on other modules

Still have questions?

Everything you need to know about the Orki MCP and how to use it day to day.

Book a demo
The declaration is produced by Orki, with its templates and calculations. The assistant helps you prepare it: it reads the results, runs the checks and flags what is missing before verification.
Yes. The assistant calls Orki's tools, which return the results calculated by the platform. It does not recalculate any impact on its own.
The built-in agent carries out complete missions in the application (modelling, report). MCP lets you query and check your LCAs from the assistant you already use, and cross-reference their results with your other documents.
No. In Claude or ChatGPT, you connect it from the settings by pasting an address and signing in to your Orki account. After that, everything happens in conversation, in plain language.
Any assistant that supports remote MCP servers: Claude, ChatGPT, Claude Code, Cursor, Mistral's Le Chat and Copilot in VS Code, among others. Availability of custom connectors depends on the plan you have with each provider.
Orki only sends your data to the assistant you have connected, and only when that assistant calls a tool. How the assistant then processes it is governed by its provider's terms and your plan: the enterprise plans of the main assistants generally exclude training on your conversations.
No, the two coexist. The built-in agent remains available in the application. MCP lets you work from the assistant you already use, with the model of your choice, and cross-reference your Orki data with your other tools.
Orki platform users, with their own account. Book a demo or talk to your Orki contact: we will show you how it works on your use cases and open your access.

Your LCAs, in conversation

In the demo, we connect an assistant to your Orki LCAs: reading results, pre-audit and emission factor search.

Book a demo