Glean

Search internal code repositories to find implementations, patterns, and contributors across the organization. Use when asked how something is implemented in other repos, where the code for a system lives, or who has been actively working on a codebase.

Identify who owns, maintains, or has expertise in a specific code area or component. Use when asked who to talk to about a system, who to request a code review from, or who has been actively working in a codebase area.

Gather architectural context about an internal system from code and documentation across the organization. Use when asked to understand a system's architecture, find its repos, or get an overview before working on it.

Assess and communicate the reliability, freshness, and authority of Glean search results before presenting them. Use when presenting Glean results that may be stale, come from informal sources, or where the user should verify before acting on them.

Search company documents, wikis, policies, design docs, and internal knowledge via Glean. Use when asked about company policies, internal specs, design docs, RFCs, or any information that lives in enterprise systems rather than the local codebase.

Find usage examples of an API, library, or code pattern across internal repositories. Use when looking for how other teams use an internal API, library, or pattern before implementing something new.

Find subject matter experts for a topic based on code contributions, document authorship, and activity signals. Use when asked who knows about a topic, technology, or system — finding real experts based on contributions rather than just job titles.

Select and use Glean MCP tools correctly — tool selection by query type, filter syntax, and best practices for all Glean tool types. Use when choosing between Glean tools, formatting queries, or applying filters for search, code, people, meetings, or email.

Configure a Glean MCP server connection in Cursor step by step. Use when the user wants to set up Glean in Cursor, add a new MCP server, or connect to a different Glean instance.

Check which Glean MCP servers are configured and active in Cursor. Use when the user wants to verify their Glean connection, list configured servers, or troubleshoot MCP connectivity issues.

Find meeting transcripts, decisions, and action items via Glean meeting search. Use when asked what was decided in a meeting, what action items came out of a discussion, or what was said about a topic in recent meetings.

Find people by name, role, team, or expertise using Glean employee search and activity signals. Use when asked who works on something, who owns a system, who to contact, or for org chart and reporting relationship queries.

Research enterprise context before plan mode — design docs, similar implementations, stakeholders, and related systems. Use when about to plan or design a feature and wanting to surface relevant RFCs, prior art, code owners, and related systems first.

Perform a structured Glean search with result vetting and quality assessment. Use when the user explicitly requests a Glean search and wants formatted results with freshness and authority indicators.

Find similar implementations and prior art for a code pattern across internal repositories. Use when checking whether something already exists internally before building it, or looking for reference implementations to follow.

Identify stakeholders who need to approve, consult on, or be informed about a change or project. Use when planning a change that affects other teams or systems and needing to know who to involve, consult, or notify.

Combine and synthesize information across multiple Glean sources — documents, code, meetings, and people — into coherent answers. Use when answering questions that span multiple source types, or when results from one source need context from another to give a complete picture.