Once connected, you can ask Glean Assistant about a meeting the same way you'd search for anything else in Glean. Grain supplies the transcript, AI notes, and action items behind the scenes.
Connect Grain to Glean
Grain MCP is listed as a vendor-provided tool inside Glean. This is a one-time setup by a Glean admin, and it applies to your whole Glean workspace.
In Glean, open the 'Admin Console.'
Click 'Add', then go to the 'Vendor provided tools (via MCP)' tab.
Search for and select 'Grain MCP' from the list of vendor-provided tools.
Review the pre-filled configuration (server name, description, server URL, transport type, and authentication method), then click 'Initiate connection'.
You'll be redirected to Grain to approve the connection for your workspace.
Back in Glean, click 'Edit settings' to review the list of tools Grain exposes.
For each tool you want available, enable it for Agents so agent creators can use it in Agent Builder, and optionally enable it for Glean so Glean Assistant can call it directly in conversation.
Click 'Save'.
Test the connection
Confirm the connection works before rolling it out to your team.
From Agent Builder:
Create a test agent.
Add a 'Plan and Execute' step and select one of Grain's tools.
Run the agent with a sample query and confirm it returns real Grain data.
From Glean Assistant:
Start a new chat.
Ask something like "Use Grain to tell me about my most recent meeting."
Confirm the assistant calls the Grain tool and the results look correct.
Note: If the connection fails, check Grain's side of the OAuth approval first, then Glean's MCP connectivity logs.
How Grain results surface in Glean
Once connected, Grain doesn't add meetings to Glean's core Search results — it isn't a content connector that crawls and indexes recordings ahead of time. Instead, it's a real-time call-out: Glean reaches into Grain at the moment of a query and pulls back the relevant meeting, transcript, or note. Grain's tools become actions that Glean Assistant and Glean Agents can call on demand:
In Glean Assistant: a user can ask a question in natural language (for example, "What did Acme Corp say about renewal timing in our last call?"), and Glean invokes the relevant Grain tool, then folds the result into its answer.
In Glean Agents: an agent builder can add a Grain tool as a step in a 'Plan and Execute' workflow, chaining it with other Glean actions, for example, pulling a Grain transcript and then passing it to a summarization step.
Every call still respects Grain's own permissions, and Glean applies no additional scoping on top. A user can only pull data from meetings they already have access to in Grain.
FAQ
Does connecting Grain add my meetings to Glean Search results? No. This integration exposes Grain's tools as actions for Glean Assistant and Agents to call. It doesn't crawl or index Grain content into Glean's Search index.
Can I control which Grain tools Glean can use? Yes. When you enable actions in Glean, you choose which tools are available to Agents and to Glean Assistant, and you can apply role-based access so only specific creators can add sensitive tools to agent workflows.
Does this work the same way as connecting Grain to Claude or ChatGPT? It uses the same underlying Grain MCP server, but Glean is acting as the MCP host instead of Claude or ChatGPT. Setup happens once at the admin level in Glean, rather than per user.