Aevia LCA Modeler

npx add-mcp 'https://app.aeviamodeler.ai/api/v1/connector/mcp'

Connect Aevia to your AI assistant

Aevia's MCP Connector lets an AI assistant you already use work with your Aevia account. The read-only MCP Connector, on every plan including the free one, searches LCA databases and Aevia's library of LCA literature and reads the work you have saved. The full MCP Connector, an add-on, also builds product systems, runs life cycle impact assessments and analyses the results. Everything it builds is saved to your Aevia workspaces, where you can open it later.

MCP — the Model Context Protocol — is the shared standard AI assistants use to reach tools that are not their own. Aevia publishes one address that speaks it, so there is nothing to download and nothing to install: you paste that address into your assistant, sign in once, and Aevia's tools appear alongside the ones it already had.

What you need

• An Aevia account. Sign-up is free.
• The read-only MCP Connector is included on every plan. The full MCP Connector is an add-on to the Base plan, and your first month switches it on — on the Demo plan's own usage limits and assistant models, which the month does not change; see Plans.
• An app that supports custom MCP connectors. Claude, ChatGPT and Gemini all do, and so do coding tools such as Claude Code, Cursor and VS Code — but each app decides which of its own accounts may add one. See below.

Which apps can do this

Every app below reaches the same address and gets the same tools. What differs is whether your account with that app is allowed to add a connector at all — that is the app's decision, not Aevia's, and it is the most common reason a connection never gets started.

App	How you connect	Available to
Claude	Sign-in	Every plan, the free one included
ChatGPT	Sign-in	Paid plans, with developer mode turned on
Gemini	Sign-in	Personal Google accounts in the United States
Claude Code, Cursor, VS Code and similar	Access key	Anyone

Sign-in means the app sends you to Aevia, you approve the connection there, and no key is ever copied anywhere. An access key is a long secret string you paste into the app's settings file yourself, for apps that have no sign-in step.

The connection address

https://app.aeviamodeler.ai/api/v1/connector/mcp

It is the same address for every app. Claude, ChatGPT and Gemini sign in with OAuth: the app sends you to Aevia to sign in and approve the connection, so there is no key to copy.

Claude

1. In Claude, open Customize → Connectors, select +, then Add custom connector.
2. Paste the connection address above and select Add.
3. Sign in to Aevia when asked, and choose what Claude may do (see below).
4. To use it, open the + menu in a conversation, choose Connectors and switch Aevia on.

Adding it once covers Claude on the web, the desktop app and the mobile apps: the connection lives on your Claude account, not on one device. Claude's free plan allows one custom connector. On a Team or Enterprise plan, an owner first adds the connector under Organization settings → Connectors; members then find it under Customize → Connectors and select Connect.

ChatGPT

1. In ChatGPT, open Settings → Security and login and turn on Developer mode.
2. Open Plugins, select +, and give the connection a name, such as Aevia.
3. Under Connection, paste the connection address above and create the connection.
4. Sign in to Aevia when asked, and choose what ChatGPT may do (see below). To use it, add Aevia from the tools menu in a new conversation.

Developer mode is available on ChatGPT Plus, Pro, Business, Enterprise and Education, on the web. It does not exist on ChatGPT's free plan, so there is no way to add a connector there — if you cannot find the setting, check which plan the account is on before looking further. In a business workspace an admin may need to allow it first.

Gemini

1. On gemini.google.com, open Settings → Connected apps.
2. Under Custom apps, choose Add a custom app.
3. Paste the connection address above and continue.
4. Sign in to Aevia when asked, and choose what Gemini may do (see below).

Google currently offers custom apps only on personal Google accounts in the United States, in English, with activity history switched on. A work or school Google account does not show the option at all. On a work account, a team administrator can instead add Aevia as a custom MCP server from Gemini's business team settings, under Manage team → Connected apps.

Claude Code, Cursor and other apps you set up by file

These have no sign-in step, so they carry an access key instead. The same steps apply to VS Code, Windsurf and any other tool configured by file.

1. In Aevia, open Settings → MCP Connector and create an access key. It is shown once; copy it then.
2. Add Aevia to your client with the connection address and the header Authorization: Bearer YOUR_KEY. For Claude Code:

   claude mcp add --transport http aevia https://app.aeviamodeler.ai/api/v1/connector/mcp --header "Authorization: Bearer YOUR_KEY"
   

3. Restart the client.

Treat an access key like a password: anyone holding it can act as you, within the access level it carries.

Choosing what the assistant may do

• Read-only — browse the engine catalogue, list what you have already saved, and read the knowledge library. Writes nothing, and is included on every plan as the read-only MCP Connector.
• Author — everything in Read-only, plus composing, importing and editing saved product systems. Writes saved objects in the workspace it is working in. Needs the full MCP Connector.
• Execute — everything in Author, plus running assessments and sensitivity and contribution analyses. These occupy the calculation engine, usually for seconds and sometimes for minutes, and count toward your daily calculation limit. Needs the full MCP Connector.

No access level spends your Aevia usage credits. Those pay for the assistant built into Aevia, which a connection from another assistant does not use.

Start with the lowest access level that does the job. You can disconnect and connect again with a different one at any time.

Where the work is saved

A connection you approve by signing in starts in a workspace Aevia creates for that app, so its work stays separate from yours. An access key works in the workspace you chose when you created it. Either way, the assistant can move to another of your workspaces when you ask it to, by name, and everything it builds is waiting for you in Aevia afterwards.

Disconnecting

Every connection is listed under Settings → MCP Connector in Aevia, and each one switches off there immediately.

If something doesn't work

• The app has no way to add a custom connector. That is the app's own gate — see which apps can do this. Nothing set in Aevia can add a menu the app does not offer.
• Your app isn't named here. Any app that supports custom MCP connectors can use the same address; there is nothing Aevia-specific to configure. It will ask either to sign in or for an Authorization header, and both are covered above.
• Some tools seem to be missing, or the assistant says it cannot build or calculate. We can only guess from here, but two causes are likely: the connection may have been made at a lower access level than the task needs, or your account may have the read-only MCP Connector but not the full MCP Connector — which is what changes when your first month ends. Your connections page shows what each connection can do.
• Anything else. Write to hello@aeviamodeler.ai.

Your data

Results of the requests you make are returned to the assistant you connected, which handles them under its own terms. What Aevia keeps about a connection, and for how long, is set out in the Privacy Policy.