Admins can now share a single MCP connection with everyone who uses a Knowledge Agent.
When you add an MCP server in Manage > Apps and Integrations > MCP Servers, you'll choose how people connect: Personal, where each person signs in with their own account, or Shared, where an admin authorizes the connection once and everyone on a Knowledge Agent that uses the server is connected automatically. Previously, every person had to sign in to every server before they could chat. Now a shared server just works, with no sign-in prompts for your team at all.This is for admins rolling out agents that take action in other tools.
If your integration runs on a service account or a single team credential, or you simply want a Knowledge Agent to work for hundreds of people without asking each of them to authorize, shared connections were built for you. Personal connections aren't changing, and they remain the right choice whenever actions should run under each individual's own account and permissions.Sharing the connection doesn't mean giving up control.
You choose the connection type deliberately when the server is created, and the account the admin authorizes with defines exactly what the connection can reach. Each person still reviews and approves the individual actions an agent wants to take on their behalf, just as they do today, so a shared credential never becomes a blank check. Guru manages the connection behind the scenes, keeping it healthy without anyone needing to re-authenticate.Next time you add an MCP server, look for the connection options in the setup form.
A good first step is a low-stakes internal tool: set it up as shared, enable it on one Knowledge Agent, and watch teammates use it in chat without a single connect prompt. If you have questions about which connection type fits a given tool, your Guru team is happy to help.