Skip to main content
Glean is the connector to reach for when the answer is somewhere inside your company rather than inside your conversation data. Rippit already holds your tickets and calls; Glean holds the wikis, docs, chat history, tickets in other systems, and the people directory around them. Connect it when the agent needs that context to explain what it is seeing.

​
What the agent gets

Broadly, four things:
  • Company knowledge. Search across everything Glean indexes, Glean’s own synthesized answers for questions that need reasoning rather than a list of links, and full document reads by URL.
  • People and meetings. Who someone is, who works on what, reporting lines, and the meeting or transcript where something was decided.
  • Personal context. The connecting user’s recent activity, and their Glean Memory.
  • Whatever else your Glean exposes. Usually the largest part. See below.
Typical uses: asking why an account is configured the way it is and getting the internal doc that explains it; finding the owner of a system your tickets keep blaming; pulling the meeting where a policy the agent keeps citing was actually decided.

​
Your tool list depends on your Glean setup

Glean’s MCP server is a gateway as much as a product. Anything your Glean admin has registered through the Glean MCP Gateway, plus any custom Glean agents your team has built, arrives as more tools on the same connection. Even Glean’s own tools depend on which sources your Glean is wired into: email and meeting search only appear if Glean has Google Workspace and your calendar. The range is wide: one tenant’s server may expose nine tools, all of them Glean’s own, and another’s over three hundred. So this page does not list tools. After connecting, open the connection under Connections → MCP Servers and read its tool list; that is the authoritative answer for your organization. Two things to look for when you do:
  • Tools that write. Glean’s own writes are limited to Memory, but a registered third-party server may expose tools that create, update, or delete in that system. Like every write tool, they arrive disabled. Review them deliberately rather than enabling in bulk.
  • The server you picked. If your organization has more than one Glean MCP server, the URL you paste decides which tools exist at all. Glean marks a default server as recommended, which is the usual choice.

​
Setup

Nothing to configure in Glean. Rippit registers itself as an OAuth client automatically, so a Full Admin only supplies the URL and signs in.
  1. In Glean, open account settings and find Third party apps and MCP. Copy your MCP server URL. It is specific to your tenant and looks like https://<tenant>-be.glean.com/mcp/<server-name>.
  2. In Rippit, go to Connections → MCP Servers, choose Glean, and paste the URL.
  3. Click connect and complete your organization’s SSO sign-in.
Rippit checks the URL points at a real Glean host before trying to connect.

​
Identity and scope

Glean’s MCP server acts as the person who authorized it, and results respect that person’s permissions in Glean. A document the connecting user cannot open in Glean does not become readable through Rippit. That makes who connects a real decision. An organization-wide connection authorized by someone with broad access extends that reach to everyone using the agent; one authorized by someone with narrow access will quietly return less than colleagues expect. Glean has no application-level token that acts as the organization rather than a person, so connecting as a service account is not an option. The scope you choose at setup decides whether Agent Apps can use the connection, exactly as with every other connector.