Connect Labguru to AI assistants (MCP) – Labguru

The Labguru MCP server lets an AI assistant such as Claude or Microsoft Copilot Studio work with your Labguru data: search, read, and create or update records, using your own account and permissions. The Labguru MCP server is part of the AI package, so it is available to labs that have the AI package.

Connect

There are three ways to connect Claude, plus Microsoft Copilot Studio (below). Pick one, follow its steps, then run the check.

Option	Use it when	What Cenevo provides
A. Claude connector (web, desktop and mobile)	You use Claude at claude.ai or in the Claude app. Recommended for most people.	Your lab's Labguru MCP address (it ends in /mcp), unless your admin already added it for the whole company
B. Claude Desktop extension	Your admin gave you a .mcpb file, or option A is blocked at your company	The .mcpb file and your Labguru address
C. Claude Code	You are comfortable in a terminal and want Labguru data inside your own scripts or analysis, or your company blocks the desktop extension and custom connectors but allows Claude Code	The MCP URL

Before you start, you need your Labguru username and password, and to be able to log in to Labguru in your browser today.

Reading or writing. Reading is on by default, but your Labguru account owner can turn it off in Labguru's AI settings. Creating or changing things (for example adding a comment or a stock item) works only if your account owner has turned on AI write access in the same settings. Write access is off by default.

Choose your region

Labguru runs two regions, and each has its own MCP server. Each server works only with accounts that sign in on its own domain, so use the one that matches your sign-in domain. The server address for your region comes with the AI package.

Region	Sign-in domain
US	my.labguru.com
EU	eu.labguru.com

Option A: Add Labguru to Claude as a connector

You do this once, and it then works on claude.ai, the desktop app and the mobile app. It needs a paid Claude plan (Pro, Max, Team or Enterprise); custom connectors are not on the free plan. On Team and Enterprise plans, only an Owner can add a new connector for the company. If you don't see Add custom connector, ask your admin to add Labguru in Admin settings → Connectors, then just click Connect.

Open claude.ai (or the Claude desktop app) and go to Settings → Connectors.
Look for Labguru in the list. If it is there, your admin already added it: click Connect and skip to step 7. If not, continue.
Click Add custom connector.
Name it Labguru. In Remote MCP server URL, paste the MCP server address for your region that came with your AI package. You can see your domain in the address bar once you log in to Labguru. If you don't have the address, ask Cenevo Support.
Click Add, then Connect next to the new connector.
A browser tab opens on your Labguru login page. Log in with your normal Labguru username and password.
On the next screen, Labguru asks if Claude may act for you. Click Authorize.
Back in Claude, the connector now shows as connected.
Start a new chat. Click the + (or tools) button under the message box and make sure Labguru is switched on.

Option B: Install the Claude Desktop extension

Use this only if your admin sent you the extension file. You only sign in once: the extension keeps you signed in and renews your login by itself. You need the latest Claude desktop app (claude.ai/download), the desktop-extension.mcpb file from your admin, your Labguru address (for example https://yourlab.labguru.com) and the free uv tool, which the extension uses to run. If your IT team manages your computer, ask them to install uv; otherwise follow the one-line install at docs.astral.sh/uv, then restart your computer.

Double-click the .mcpb file. Claude Desktop opens and shows the Labguru extension. (Or go to Settings → Extensions and drag the file into the window.)
Click Install.
Fill in the settings. Labguru Instance URL: your Labguru address, for example https://yourlab.labguru.com. Do not add /mcp at the end here.
Click Save and make sure the extension is switched on.
Your browser opens on the Labguru login page. Log in, then click Authorize. The page says you can close the tab.
Quit Claude Desktop completely and open it again.

If Add custom connector is greyed out ("Ask an organization owner to add this for your team") and the extension won't install, ask your admin to add Labguru for your company or to allow the extension.

Option C: Connect Labguru in Claude Code

You need Claude Code and a Claude plan or API access that includes it.

Add the Labguru MCP server to Claude Code using the MCP server address for your region that came with your AI package. The easiest way is to ask Claude to do it: start Claude Code and say, for example, "Add a new MCP connector called labguru with this URL: [your MCP server address]".
In Claude Code, type /mcp and select labguru. It shows as "needs authentication".
Choose Authenticate. Your browser opens on the Labguru login page. Log in with your normal Labguru username and password, then click Authorize.
Back in Claude Code, /mcp now shows labguru as connected.

You only sign in once. To sign in as a different user, in /mcp select labguru and choose Clear authentication, then authenticate again. If your company manages Claude Code settings, your admin may need to allow the Labguru server URL.

Check that it works

Send these three messages in a new chat, in this order.

Send this	A good answer
Check my Labguru connection and tell me who I'm signed in as.	Your name and your Labguru account
List my Labguru projects.	Your projects, the same ones you see in Labguru
Show my five most recent experiments.	Five experiments with their names and dates

If all three work, you're done. Claude may ask before it uses a Labguru tool for the first time: click Allow (or Always allow for read-only tools). The assistant can only see and change what your Labguru user is allowed to. Sign out or remove the connector to revoke access.

Connect Microsoft Copilot Studio

Copilot Studio cannot sign in to an MCP server directly. A custom connector, a small adapter built in Power Apps, handles the sign-in, and your agent calls the connector. Allow about 10 minutes. You need a Labguru account on your region's sign-in domain, and permission to create custom connectors in your environment (the Environment Maker role). If you lack it, ask your Power Platform administrator.

Step 1: Add the Labguru MCP server

In Copilot Studio, open your agent, then go to Tools, select + Add a tool, then New tool, then Model Context Protocol.
Fill in the dialog (see the table below) and select Create. Copilot Studio makes the custom connector.

Field	Enter
Server name	Labguru MCP
Server description	Labguru MCP server
Server URL	The MCP server address for your region, provided with your AI package
Authentication	OAuth 2.0
Type	Dynamic discovery

Choose Dynamic discovery. Copilot Studio reads Labguru's sign-in settings from the server URL, so you need no client ID, client secret or redirect URL.

Step 2: Create the connection

When prompted, create a new connection to the Labguru MCP tool.
A pop-up opens the Labguru login page. Sign in, then select Authorize.
The pop-up closes and the connection is saved.

If the pop-up does not open, allow pop-ups for copilotstudio.microsoft.com in your browser.

Step 3: Add the tool to your agent

Open your agent in Copilot Studio, or create one under Agents, then select + Create.
Open the Tools tab and select + Add a tool.
Select the Model Context Protocol filter and clear the search box.
Select Labguru MCP. If it does not appear, search for Labguru or your connector's name.
Confirm the connection shows a green tick, then select Add and configure.
On the settings page, scroll to Tools. You should see 13 Labguru tools, such as labguru_eln, labguru_collections and labguru_utilities. Select Save if a Save button appears.

Verify the connection

Type this	It works if
Check my Labguru authentication	It confirms you are signed in to Labguru
List my Labguru projects	It shows your real Labguru projects

To see what happened behind an answer, select the activity-map icon in the test chat. It shows which Labguru tool was called and what it returned.

Publish and share

Select Publish, then add a channel such as Microsoft Teams. Each person signs in to Labguru the first time they use the agent and sees only their own data.

What you can ask

You don't need any special words. Ask the way you would ask a colleague, and be specific about names, dates and projects.

"Find plasmids in our collection that contain GFP."
"What's stored in box A3?"
"Search Labguru for experiments about cell viability."
"Which equipment do we have for centrifugation?"
"Summarize the protocol 'Western blot v2' step by step."
"Find experiments mentioning CRISPR from the last month."
"Convert this document into a protocol."

The assistant sees only what your Labguru account can see. Creating or changing things works only if your account owner has turned on AI write access. Teams, tags, requests and papers are not available to MCP yet, and neither is booking equipment, checking availability or exporting a report as PDF. Use Labguru directly for those. Be specific, and ask the assistant to confirm before it changes anything.

Troubleshooting

Most problems are solved by signing in again or starting a new chat. Try these first, whatever the problem: start a new chat (old chats can hold on to an expired connection); check you can log in to Labguru in your browser with the same account; disconnect and reconnect (in Claude: Settings → Connectors → Labguru → Disconnect, then Connect; with the desktop extension, switch it off and on, then restart Claude).

Signing in

What you see	What to do
"The redirect URI is invalid" or "doesn't match" on the Labguru page	The setup on Labguru's side is incomplete. Send a screenshot to your admin.
"Client authentication failed" or "unknown client"	The sign-in setup on Labguru's side is wrong. Send a screenshot to your admin.
The browser login page never opens (option B)	Quit and reopen Claude Desktop. If it still doesn't open within a minute, check the extension is switched on. The sign-in waits 5 minutes before it gives up.
You signed in, but the extension still says you're not signed in (option B)	Your browser blocked the return to your computer, or another program uses the same port (8765). Close other apps, restart Claude Desktop and sign in again.
Copilot or Claude keeps asking you to sign in	Close the chat, open a new one and sign in once more. If it keeps looping, sign out of Labguru in your browser, then try again.
"No Labguru OAuth token provided"	You are not signed in. Sign in again (see the steps above).

Connecting

What you see	What to do
Claude says it can't reach the server, or the connector shows an error	Check the address ends in /mcp and starts with https://, with no space or slash after mcp.
No Add custom connector button	Your company lets only Owners add connectors, or you are on the free plan. Ask your admin.
Labguru does not appear in the chat's + or tools menu	Switch it on in that menu. If it isn't listed, the connector is not connected: go back to option A, step 5.
"No Labguru URL configured"	Server setup issue. Send the exact message to your admin.
Copilot says it's not connected, or has no Labguru tool	Ask your admin to check the agent is published and shared with you.
labguru is not listed in /mcp (option C)	Add the server again, from the same project folder where you start Claude Code, and check the URL.

Desktop extension (option B)

What you see	What to do
"spawn uv ENOENT", "uv: command not found" or "server disconnected" right after install	The uv tool is missing or Claude can't find it. Install it (see option B), then restart your computer, not just Claude.
The extension worked, then stopped after a few minutes	Open Settings → Extensions → Labguru and check for an error. Switch it off and on.
You want to sign in as a different Labguru user	Quit Claude Desktop, delete the .labguru-mcp folder in your home folder, then reopen Claude and sign in.
The first start is slow	Normal: the first launch downloads what the extension needs, which can take a minute or two.

Using it

What you see	What to do
"MCP write access is disabled for this Labguru account"	Reading works, but creating or changing is off for your lab. Ask your Labguru account owner to turn on MCP write access under Settings → AI in Labguru.
It can't find something you know exists	It sees only what your account can see. Open the item in Labguru with the same account. If you can see it, ask again with the exact name or ID.
The answer is cut short or misses items	Ask for fewer items at a time, or add a filter such as a project, date or owner.
"Not available" for teams, tags, requests or papers	Labguru doesn't offer these to MCP yet. Do them in Labguru directly.
Booking equipment, checking availability or exporting a report as PDF fails	Also not available to MCP yet. Use Labguru directly.

Copilot Studio issues

What you see	What to do
Create is greyed out or fails	You need the Environment Maker role. Ask your Power Platform administrator.
"Not Found" or a 307 redirect when the agent calls Labguru	The server URL is not exact for your region. Check the entry in Step 1 against the address you were given.
Sign-in works but Labguru rejects every call	The connector uses a different OAuth app from the MCP server. Use the server's own app, then recreate the connection.
Settings changed but nothing is different	Existing connections keep their old settings. Delete the connection and create a new one.
The connector is missing from the tool list	Confirm you are in the environment where you created it, use the Model Context Protocol filter, and search for Labguru. New connectors can take a few minutes to appear.
The tool is added but nothing happens	Turn on generative orchestration in the agent's settings.

Still stuck? Contact your Labguru or IT admin, or Cenevo Support. To get a fast answer, send them: which option you used (A, B or C, or Copilot Studio) and whether you're on Mac, Windows, web or Teams; the exact error message, or a screenshot; the step where it went wrong; and the time it happened, so they can find it in the logs. Never send your Labguru password, and never paste it into a chat with Claude or Copilot. The assistant never needs it.