Official Glean plugins for Cursor, enabling enterprise knowledge integration directly in your development workflow.
# Install the foundation plugin first (required)
/add-plugin glean-core
# Then install the feature plugins you need
/add-plugin glean-search
/add-plugin glean-code
/add-plugin glean-people
Then configure your Glean MCP connection — add your server to ~/.cursor/mcp.json:
{
"mcpServers": {
"glean": {
"url": "https://YOUR-INSTANCE-be.glean.com/mcp/YOUR-SERVER-NAME"
}
}
}Replace YOUR-INSTANCE with your Glean instance name and YOUR-SERVER-NAME with the server name provided by your Glean administrator. Restart Cursor after editing — OAuth authentication is handled automatically on first use.
| Plugin | Description | Docs |
|---|---|---|
| glean-core | Foundation plugin with MCP setup skills, tool guidance, and result-vetting rules. Required by all other plugins. | README |
| glean-search | Enterprise search across docs, Slack, email, and more | README |
| glean-code | Cross-repo code exploration, examples, and ownership | README |
| glean-people | Find experts and identify stakeholders | README |
| I want to... | Install |
|---|---|
| Search company docs, wikis, and Slack | glean-core + glean-search |
| Find code examples or prior art across repos | glean-core + glean-code |
| Research architecture before planning a feature | glean-core + glean-code |
| Find who knows about a topic or owns a system | glean-core + glean-people |
| Identify stakeholders for a change | glean-core + glean-people |
| All of the above | Install all plugins |
- Cursor (latest version)
- A Glean account with MCP access
- Your Glean MCP server URL (format:
https://[instance]-be.glean.com/mcp/[server-name])
Note: Glean MCP server URLs are instance-specific and cannot be bundled with the plugin. Your Glean administrator can provide your server name.
MIT — see LICENSE for details.
