Connect enterprise AI assistants (Copilot, Gemini)
This page covers the central setup for Microsoft 365 Copilot, Copilot Studio and Google Gemini. Permissions, limits and trust questions are the same as on Connect AI assistants (MCP).
Connect Microsoft 365 Copilot
With Claude and ChatGPT, each person sets up their own connection. Microsoft 365 Copilot works differently: someone with administrator rights registers Librario centrally once, and the connector is then available to everyone who is licensed for it. Every person still signs in to Librario with their own Librario user the first time they use it, so everyone who searches Librario from Copilot needs a Librario user.
A user comes into being through an invitation in the user management or, with single sign-on with Microsoft, automatically on the first sign-in from Copilot, as long as your plan has free seats. Once all seats are taken, the person sees a notice instead of the consent screen, and your administrators and librarians receive an email. Plan the seats before the rollout.
Microsoft’s Copilot landscape is tangled: the products have been renamed several times, and there are two unrelated ways to connect an MCP server like Librario:
- Federated connector: an administrator registers the Librario MCP URL once in the Microsoft 365 admin center. Librario then appears for every licensed person in Microsoft 365 Copilot Chat, the Researcher agent, Copilot in Excel and Cowork. Each person needs a Microsoft 365 Copilot license. Access is read-only (search, detail lookup, file download); write actions are not possible.
- Copilot Studio agent: if your organisation builds its own agents, you can add Librario as an MCP tool inside a Copilot Studio agent instead. This is more flexible but needs a separate Copilot Studio license. It is aimed at people who develop agents.
With Microsoft 365 Copilot licenses, the federated connector is the obvious path. It is part of advanced AI controls. Copilot Studio is a separate product with its own license. Librario is then available only inside your agent, not in Copilot Chat or the Researcher agent. With Dynamic discovery, Copilot Studio does not need advanced AI controls. Both paths are described below.
Set up the federated connector (admin)
The federated connector does not register itself with Librario. Microsoft asks for a client ID and client secret, so the connector needs an OAuth client issued by a Librario administrator, which is part of advanced AI controls.
- You need the Global Administrator or AI Administrator role in the Microsoft 365 admin center, plus access to the Teams Developer Portal.
- In Librario, an administrator creates an OAuth client for the “AI assistants (MCP)” surface, with the callback URL
https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect. - In the Teams Developer Portal, open Tools → OAuth client registration and add a new registration: the client ID and client secret, Librario’s authorization URL as the authorization endpoint, the token URL as both the token endpoint and the refresh endpoint, and
library:read assets:readas the scopes. Leave PKCE enabled. Note the OAuth client registration ID. - In the Microsoft 365 admin center, open Copilot → Connectors, choose Create a new connector → Connect to MCP server, and enter a display name, your Librario MCP URL, and the registration ID.
- Release the connector, optionally via a staged rollout to selected groups first, then to everyone.
Choose OAuth 2.0 as the authentication method. Microsoft’s second option, Microsoft Entra SSO, works only for MCP servers that accept Microsoft Entra tokens. Librario’s MCP server accepts only access tokens issued by Librario itself.
Microsoft changes the menus of this still-young area frequently. For the current, click-by-click instructions, see Microsoft’s documentation: Set up custom federated connectors.
Use the federated connector (end user)
Once an administrator has released the connector, Librario appears as a source in the Researcher agent and in Microsoft 365 Copilot Chat, where you connect it under Settings → Sources. On first use, Copilot signs you in to Librario. The same OAuth sign-in and consent screen as for Claude and ChatGPT. You sign in with your own Librario user, and Copilot searches with your permissions. After that you search in natural language, for example: “Find publications about steel column buckling since 2020.”
What to keep in mind
As of September 2026, labels and menu paths in the admin center may still change. Access is read-only and available only in certain Copilot surfaces (Copilot Chat, Researcher, Copilot in Excel, Cowork). Every person using it needs a Microsoft 365 Copilot license; Copilot Studio licenses and pay-as-you-go billing do not cover federated connectors. The setup above follows Microsoft’s documentation and has not yet been verified on a real Microsoft 365 tenant. If the OAuth client registration form asks for a base URL, enter your Librario MCP URL.
Copilot Studio: Librario as an MCP tool
Organisations that build their own agents add Librario directly to a Copilot Studio agent. You need a Copilot Studio license for this.
Beta: Copilot Studio
Copilot Studio support is in beta. Menu names in Copilot Studio can change. Tell us how it runs for you via the contact page.
Copilot Studio offers two kinds of sign-in: Dynamic discovery and Manual. Use Dynamic discovery. Copilot Studio then registers itself. Nobody has to obtain credentials beforehand.
- In the agent, open Tools → Add a tool → New tool → Model Context Protocol.
- Enter a server name, a description, and your Librario MCP URL.
- For authentication choose OAuth 2.0, then Dynamic discovery. Copilot Studio reads Librario’s discovery documents and registers itself. It asks for nothing further.
- Click Create, then Next. Create a new connection. Librario shows the sign-in and the consent screen. Sign in and click Allow access. On the consent screen, Copilot Studio appears as Credential Manager: that is the name it registers with in Librario.
- Open the tool’s settings under Details → Additional details. Leave the default End user credentials there. Every person then signs in with their own Librario user. With Maker-provided credentials (the maker is the person who builds the agent), everyone acts as one person, see the warning below.
Maker-provided credentials: everyone acts as one person
With Maker-provided credentials, every colleague who uses the agent acts with the Librario user and permissions of the person who built it. The account’s audit log (with advanced AI controls) names that person for everything the agent does. Which colleague actually asked cannot be read from it. All colleagues also share that person’s request limit: when it is exceeded, Librario briefly rejects further requests. Favourites the agent marks all land in that one person’s favourites. If that person is a librarian or administrator and granted “Manage catalogue” or “Manage tasks”, everyone who uses the agent can edit publications and tasks and close tasks through it, even without such a role of their own. End user credentials is the recommended setting.
Administrators have two options: change the role of the person who built the agent, and the agent’s permissions follow on the next call. Or switch the MCP connection off for the account: in the account settings, under Access for AI assistants, choose AI assistants are disabled for this account.
For your IT: the person building the agent makes this choice, and Microsoft allows both options by default. With “Maker-provided credentials” and the permissions “Manage catalogue” or “Manage tasks”, everyone who uses the agent edits your catalogue and tasks with the rights of the person who built it. To make sure no agent runs on someone else’s Librario user, allow only End-user credentials under Control maker credential options for the environment in the Power Platform admin center. This also covers Power Automate flows an agent uses as a tool. Details: Control maker-provided credentials for authentication. Outside agents, the same applies to Power Automate flows shared with their owner’s embedded connection: they run on that person’s Librario user. The federated connector has no shared sign-in.
Details: Connect your agent to an existing MCP server.
Manual OAuth configuration
Copilot Studio cannot use the Manual type under OAuth 2.0 with Librario: the manual form sends no PKCE, and Librario requires PKCE from every client. Choose Dynamic discovery as described above; Copilot Studio then registers itself and needs neither a Client ID nor a Client Secret.
Connect Google Gemini
With Google the answer depends on the Gemini product, and the most important limitation goes first: Gemini in Gmail, Docs and the other Google Workspace apps cannot connect a third-party MCP server. With a work account, Gemini offers only a curated catalogue of Google and partner integrations, with no setting to enter the Librario MCP URL. Don’t go looking for one there.
These paths do work:
- Gemini Enterprise: a separate, separately-licensed Google Cloud product (not the same as “Gemini for Workspace”). Here an administrator registers Librario as a “custom MCP server data store”. The feature is generally available; in the Business edition of Gemini Enterprise it is still in Preview.
- Gemini CLI: Google’s open command-line tool. It lets an individual connect Librario without any admin involvement.
- The Gemini app with a personal Google account: at gemini.google.com, personal accounts can add a custom app by its MCP URL under Settings → Connected Apps. Google currently offers this only in the US, in English and to people aged 18 or over, and not for work or school accounts. We have not yet tested this path with Librario.
Set up Gemini Enterprise (admin)
Gemini Enterprise does not register itself; it needs an OAuth client issued by an administrator, which is part of advanced AI controls. Setup happens in the Google Cloud console, not the Google Workspace Admin console.
- Lift the organisation policy that blocks custom MCP server data stores by default, and grant the Discovery Engine Editor IAM role. If your organisation restricts outbound domains or data sources, also allow the Librario MCP, authorization and token URLs.
- Register Gemini Enterprise as an OAuth client with the callback URL
https://vertexaisearch.cloud.google.com/oauth-redirect, and note the client ID and client secret. Both come from the same page as Copilot Studio: OAuth clients for integrations. - Under Data Stores → Create data store → Custom MCP Server, create an entry with your Librario MCP URL, the OAuth endpoints (authorization and token URL), client ID, client secret, and scopes. Tick PKCE support.
- Complete the OAuth sign-in, then explicitly enable the tools you want. None are enabled by default.
For the current, click-by-click instructions, see Google’s documentation: Set up your custom MCP server data store.
Once the data store is set up, Librario is available to users as a source in Gemini Enterprise. They search in natural language, and the agent calls the enabled Librario tools when needed. According to Google, Gemini Enterprise acts on behalf of a user; the scopes define what it may do in Librario.
Use Gemini CLI (developer)
If you work with the Gemini CLI, add the Librario MCP URL as an MCP server in the CLI configuration. The Librario tools are then available to the model in every CLI session. This path needs no admin setup.
What to keep in mind
As of September 2026, Gemini Enterprise’s custom MCP server feature is generally available, and still a Preview in the Business edition. Its scope, menus, and labels may still change. The setup above and acting on behalf of each user follow Google’s documentation and have not yet been verified on a real Google Cloud project. Gemini Enterprise is a separate product, licensed separately from Google Workspace: the Gemini embedded in Gmail and Docs does not support connecting external MCP servers.