⚠️ The MCP is in early development. Features, setup steps and the questions your assistant can answer are still changing, so parts of this article may look different in your client from one release to the next.
Overview
The MCP is the bridge between an AI assistant and your Luminovo data. Once connected, your assistant can read that data, answer questions about it, generate reports and take action in Luminovo on your behalf.
The MCP endpoint is: https://mcp.luminovo.com/mcp
Where to find it
You set the MCP up in your AI assistant, not in the Luminovo web app. The connection is added as a remote MCP connector in Claude, Microsoft 365 Copilot or any other client that supports one, and you sign in there with your normal Luminovo account.
Prerequisites
A Luminovo account – the same login you use for the Luminovo web app, for example
demo.luminovo.com.An MCP-capable AI assistant – Claude, Microsoft 365 Copilot, or another client that supports remote MCP connectors.
Admin rights, for a company-wide rollout only – a workspace owner in Claude, or a Microsoft 365 Global Administrator or AI Administrator for Copilot. Individual users who connect to an already registered connector do not need this.
There are no API keys to create or paste. Authentication runs over standard remote-MCP OAuth.
Step-by-step guide
Claude (recommended)
Register the connector – workspace owner, one-time:
In Claude, open Organization settings → Connectors, then click Add → Custom → Web.
Add the Luminovo MCP server URL:
https://mcp.luminovo.com/mcp.Once the connector is registered for the organization, members can connect to it themselves.
Connect – each user:
In Claude, open Customize → Connectors and add the Luminovo connector.
Sign in with your Luminovo product account – not with a Google login.
Select the tenant you want to work with. One connection covers one tenant.
Run a smoke test: ask "Which Luminovo tenant am I connected to?" If your assistant names your tenant, the connection is working.
Microsoft 365 Copilot
ℹ️ The MCP works in Microsoft 365 Copilot, but the Copilot integration is still rolling out. Results can be less consistent than in Claude.
Before you start:
An administrator with the Global Administrator or AI Administrator role in Microsoft 365, who can also open the Teams Developer Portal.
A Microsoft 365 Copilot license for every user who should use Luminovo.
In the Microsoft 365 admin center, under Agents → Settings → Agent and plugin access, the option Allow agents and plugins built by your organization is selected. If you leave it cleared, you can still turn on the Luminovo connector on its own after you create it.
Under Agents → Settings → User access, the users who should get Luminovo are included.
Each user has a Luminovo account. You do not need any Luminovo API keys.
Step 1: Create the OAuth registration – administrator, one-time, about five minutes:
The connector signs users in to Luminovo through an OAuth registration. This registration must live in your own Microsoft 365 organization. A registration from another organization, including one from Luminovo, does not work.
Open the Teams Developer Portal and sign in with your work account.
Go to Tools → OAuth client registration and click Register client (or New OAuth client registration). The direct link is dev.teams.microsoft.com/tools/oauth-configuration/new.
Fill in the fields with the values below, then click Save.
At the top of the saved registration, copy the OAuth client registration ID. The ID is 100 characters long and ends with
=. Copy all of it, because you need it in step 2.
Registration name:
LuminovoBase URL:
https://mcp.luminovo.com/mcpRestrict usage by org:
My organization onlyRestrict usage by app:
Any Teams appClient ID:
luminovo-copilot-{company}, for exampleluminovo-copilot-acmeClient secret: any value, for example a randomly generated string
Authorization endpoint:
https://mcp.luminovo.com/authorizeToken endpoint:
https://mcp.luminovo.com/tokenRefresh endpoint:
https://mcp.luminovo.com/tokenScope: leave empty
Enable Proof Key for Code Exchange (PKCE): on
Client password authentication method:
HTTP Basic authentication
ℹ️ Microsoft requires a client secret, but Luminovo does not use it. PKCE and the Luminovo login of each user secure the sign-in. Pick your own client ID as shown above, and do not copy one from another organization.
Step 2: Create the connector – administrator, one-time, about five minutes:
Open the connectors page in the Microsoft 365 admin center. You can also go to Copilot → Connectors and open the Gallery tab.
Under Created by your org, click Add on the Create a new connector tile.
Under Connect to MCP server, click Add.
Fill in the fields with the values below.
Click Authorize and log in to Luminovo.
Go back to the form, click Create, then click Done.
Open Connectors → Your connections and check that Luminovo is listed. You do not need to sign in again on this page.
Display name:
LuminovoDescription:
Luminovo MCPBase URL:
https://mcp.luminovo.com/mcpAuthentication:
OAuth 2.0Developer name:
LuminovoWebsite:
https://luminovo.comPrivacy policy:
https://luminovo.com/legal/imprint-privacyTerms of use:
https://luminovo.com/legal/gtcReference ID (OAuth registration ID): the ID you copied in step 1, including the
=at the end
Optional: roll out to a pilot group first:
In Your connections, select the Luminovo connector.
Click Staged rollout, choose Users or Groups, and add your pilot group.
When the pilot works, click Deploy to all users.
Changes can take up to 10 minutes to reach users. Users may need to refresh Copilot or start a new chat before Luminovo appears.
Step 3: Connect – each user, once:
Open Microsoft 365 Copilot.
Click ... (more options), then Settings → Sources.
Search for Luminovo, select it, and click Connect.
Sign in with your Luminovo account, the same one you use for the Luminovo web app.
Select the Luminovo tenant you want to work in and confirm. A confirmation screen shows that Luminovo is connected.
In a new chat, click + and add Luminovo as a data source.
Run a smoke test: ask "Which Luminovo tenant am I connected to?" If Copilot names your tenant, the connection is working.
Using Luminovo in Copilot:
Before Copilot creates or changes anything in Luminovo, it asks for your approval: Allow once, Allow for conversation, or Always allow. You can change this later under Settings → Sources → Luminovo.
One connection covers one tenant. To switch, click Disconnect under Settings → Sources → Luminovo and connect again with the other tenant.
Building Luminovo apps with their own user interface does not work in Copilot yet.
ChatGPT
ChatGPT reaches the Luminovo MCP through a custom plugin. On Business and Enterprise workspaces, an admin has to allow custom MCP connectors in workspace settings before anyone can add one.
Add it (web):
Settings → Security and login → turn on Developer mode. OpenAI has moved this toggle more than once; if it isn't there, search the settings for “developer”.
Go to Settings → Plugins → Browse plugins (or
chatgpt.com/plugins) and click the plus button next to the search bar.Then click Create app → Create MCP App
Fill in the form:
Name: Luminovo
Connection URL:https://mcp.luminovo.com/mcp
Authentication: OAuthTick the confirmation box and continue, then sign in with your Luminovo account.
Pick the tenant you want to work with.
Add it (desktop app): Settings → Plugins → MCP tab → Add server. Set Type to Streamable HTTP and URL to https://mcp.luminovo.com/mcp , save, then click Authenticate next to the server and sign in.
Use it: Open a new chat, then smoke test: “Which Luminovo tenant am I connected to?”
Other clients
The MCP works with any client that supports remote MCP connectors, including ChatGPT, Cursor, VS Code, Claude Code and Codex. The principle is always the same: point the client at https://mcp.luminovo.com/mcp and sign in with your Luminovo product account over standard OAuth. Only the steps for adding a connector differ from client to client, so check your client's own MCP documentation, or get in touch with us via the help chat.
Working with more than one tenant
A connection is scoped to a single Luminovo tenant. To switch tenants, you can disconnect the connector and add it again with the other tenant. To work with two or more tenants at the same time – for example to move a BOM from one to another without swapping credentials by hand – add a separate connection for each one, using a distinct URL:
Add a new connection pointing at
https://mcp.luminovo.com/mcp/{name}, where{name}is any short label you pick, for examplefinland,germanyorsite-b.Authenticate that connection with the Luminovo account for that tenant, then select the tenant.
Repeat for the next tenant with a different
{name}.
You end up with several Luminovo connections side by side, and your assistant can work across them in one conversation.
ℹ️ The suffix only makes the URL distinct. MCP clients tie each OAuth session to a URL and reject a duplicate, so a distinct URL is what lets you hold separate tenant sessions at the same time. The label is never read as your tenant or your identity – each connection still picks its own tenant at login.
First things to try
Questions and reports work well today and need nothing beyond the connection:
Ask a question:"Which parts have the highest savings potential across my active projects?" or "What is the total value of components at risk in this BOM?"
Generate a report:"Build a sourcing performance report for my top projects and give me a shareable link."
Troubleshoot sourcing:"Why is this line item not getting offers?" and let your assistant walk the BOM and the sourcing setup.
Reuse a report: save it as a re-runnable script, so you can run it again with one request.
Clean a small BOM: ask your assistant to check and tidy a small BOM before you import it.
Once you are comfortable, ask your assistant to build a simple app, such as a KPI dashboard or an assembly overview, hosted inside Luminovo.
Troubleshooting
You need a different tenant: disconnect the connector, add it again and select the other tenant. To use several tenants at once instead, see Working with more than one tenant above.
Your tenant is not in the list: the MCP only knows a tenant by its canonical tenant name, not by a brand name, a customer name or an internal nickname. Look up the canonical name and try again with that – your Luminovo contact can confirm it for you.
Large BOM uploads: these are not fully supported yet, so stick to smaller BOMs for now.
Microsoft 365 Copilot
The option to change data sources is missing: the user needs a Microsoft 365 Copilot license to connect Luminovo as a data source.
Luminovo does not appear under Sources: check that the user has a Copilot license, is in the staged rollout and in User access, and that the connector is turned on. Wait up to 10 minutes, then refresh Copilot.
Copilot says Luminovo is not available in this chat: start a new chat and mention Luminovo in your question.
You signed in with the wrong Luminovo account: on the Luminovo sign-in page, select Sign in with a different account or Sign out of Luminovo in this browser, then connect again.
The admin center rejects the registration ID: if Authorize shows The requested resource does not exist, the ID does not belong to a registration in your organization. Use the ID of the registration you created in step 1, and check that you copied all of it, including the
=at the end. If it still fails, contact us via the help chat.Your company uses single sign-on: on the Luminovo sign-in page, select Continue with SSO and enter your tenant name (the part before
.luminovo.com) and your email. If Luminovo emails you a sign-in code, use the email-code option.
Getting help
Stuck, or have an idea for something to automate or build? Reach out via the help chat or to your Luminovo contact. We are actively working with early customers to shape what the MCP does, and we are happy to build a first app or script together with you.