⚠️ 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 Teams 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, go to Organization settings → Connectors → Add → Custom → Web.
Add the Luminovo MCP server URL:
https://mcp.luminovo.com/mcp.Once the connector is registered for the organisation, members can connect to it themselves.
Connect – each user:
Open Customize in Claude 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
Upload the app package – IT administrator, one-time, around five minutes:
Go to the Teams Admin Center → Teams apps → Manage apps.
Click Upload new app and upload the Luminovo app package. Ask your Luminovo contact for the current
.zipfile.Assign the app to your test users through an app setup or permission policy. Allow up to a few hours for the assignment to propagate.
First use – each user:
Open Microsoft 365 Copilot and pick the Luminovo agent from the agent list.
On your first request you are asked to sign in – use your normal Luminovo account.
Run a smoke test: ask "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.
Automate a report: save it as a re-runnable script, then schedule it – every Monday at 5am, for example – so the result is waiting for you.
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.
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.