steve-calvert-glean · Oct 28, 2026 · Oct 29, 2026 · Oct 29, 2026 · Oct 29, 2026
@@ -8,15 +8,41 @@
 Official Glean plugins for [Claude](https://claude.com) — enterprise knowledge,
 search, people, code, and meetings.
 
-> **Surface support:** The shared skills are designed to work across Claude Code,
-Claude Desktop chat, and Claude Cowork. Hooks and supporting agents require host
-support: Claude Code and Cowork support them, while Claude Desktop chat does not
-run them. The plugin provides a local Glean MCP server where the host supports
-bundled MCP; otherwise, configure the remote server in the host's MCP settings.
-The automated checks validate package structure, not full runtime parity in every
-host.
+## Quick start (new install)
+
+### Claude Code
+
+```
+/plugin marketplace add gleanwork/claude-plugins
+/plugin install glean@glean-plugins
+/plugin install glean-dev-docs@glean-plugins
+```
+
+Then ask Claude: `Set up Glean for me`. Enter your work email when asked, then
+finish signing in in your browser. Skills auto-trigger by task.
+
+### Claude Desktop, chat and Cowork
+
+Open **Customize → Plugins**, add the `gleanwork/claude-plugins` marketplace,
+and install **Glean** and **Glean Developer Docs**. The skills load here, but
+the `glean` plugin's Glean tools run only in Claude Code. Add Glean as a custom
+connector, using your Glean MCP server URL, and the skills use it. The
+[glean plugin README](plugins/glean) shows what works on each surface.
 
-## ⚠️ v3.0.0 — plugins consolidated (one-time migration)
+## Plugins
+
+| Plugin | Description |
+|--------|-------------|
+| **[glean](plugins/glean)** | Enterprise knowledge — search docs/Slack/email, cross-repo code exploration, people & experts, meeting prep & catch-up, onboarding, productivity. |
+| **[glean-dev-docs](plugins/glean-dev-docs)** | Search Glean's public developer documentation — APIs, SDKs, MCP, and integration guides. |
+
+## Requirements
+
+- A Glean account with MCP access
+- For Glean tools in Claude Code: [Node.js](https://nodejs.org) 22 or later
+- For Claude chat and Cowork: your Glean MCP server URL (find it at [app.glean.com/admin/about-glean](https://app.glean.com/admin/about-glean)); format: `[server-url]/mcp/[server-name]`
+
+## Upgrading from v2 (one-time migration)
 
 The commands below are for Claude Code. In Claude Desktop or Cowork, use
 **Customize → Plugins** to remove the old marketplace and install the consolidated
@@ -60,40 +86,6 @@ Restart Claude Code if prompted. `glean` carries everything the old plugins did.
 
 </details>
 
-## Quick start (new install)
-
-### Claude Code
-
-```
-/plugin marketplace add gleanwork/claude-plugins
-/plugin install glean@glean-plugins
-/plugin install glean-dev-docs@glean-plugins
-```
-
-Then set up Glean by prompting the harness, for example: `Set up Glean for me`.
-Complete the browser OAuth flow when prompted. Skills auto-trigger by task.
-
-### Claude Desktop or Cowork
-
-Open **Customize → Plugins**, choose **Add marketplace**, and add
-`gleanwork/claude-plugins`. Install **Glean** and **Glean Developer Docs**.
-
-Then ask Claude to `Set up Glean for me` and complete the browser OAuth flow
-when prompted. Skills auto-trigger by task.
-
-## Plugins
-
-| Plugin | Description |
-|--------|-------------|
-| **[glean](plugins/glean)** | Enterprise knowledge — search docs/Slack/email, cross-repo code exploration, people & experts, meeting prep & catch-up, onboarding, productivity. |
-| **[glean-dev-docs](plugins/glean-dev-docs)** | Search Glean's public developer documentation — APIs, SDKs, MCP, and integration guides. |
-
-## Requirements
-
-- A current Claude host that supports plugins: [Claude Code](https://claude.com/claude-code), [Claude Desktop](https://claude.com/download), or [Claude Cowork](https://claude.com/product/cowork)
-- A Glean account with MCP access
-- Your Glean MCP server URL (find it at [app.glean.com/admin/about-glean](https://app.glean.com/admin/about-glean)); format: `[server-url]/mcp/[server-name]`
-
 ## Support
 
 - [Glean MCP Documentation](https://docs.glean.com/mcp)

@@ -1,6 +1,6 @@
 # Glean Developer Docs
 
-Search the public [Glean developer documentation](https://docs.glean.com) — APIs, SDKs,
+Search the public [Glean developer documentation](https://developers.glean.com) — APIs, SDKs,
 MCP, authentication, indexing, and integration guides for building *with* Glean.
 
 This is a separate, focused plugin for people building on the Glean platform. For
@@ -31,7 +31,7 @@ It searches the public developer documentation and returns cited answers.
 
 ## Support
 
-- [Glean Developer Documentation](https://docs.glean.com)
+- [Glean Developer Documentation](https://developers.glean.com)
 - [GitHub Issues](https://github.com/gleanwork/agent-plugins/issues)
 
 ## License

@@ -1,7 +1,32 @@
 # Glean for Codex
 
-Official Glean plugin for [Codex](https://developers.openai.com/codex) — enterprise search,
-code exploration, and people discovery directly in your development workflow.
+Official Glean plugin for [Codex](https://developers.openai.com/codex). Search
+your company's knowledge, explore code across repos, find people and experts,
+and prepare for meetings, right in your terminal.
+
+## Where it works
+
+The plugin has two parts:
+
+- **Skills** that Codex loads from the plugin.
+- **Glean tools** from a local MCP server that the plugin starts.
+
+| Surface                          | Skills            | Glean tools               |
+| -------------------------------- | ----------------- | ------------------------- |
+| Codex CLI                        | Yes               | Yes, from the plugin      |
+| Codex in the ChatGPT desktop app | Not supported yet | Not supported yet         |
+| Codex IDE extension              | No                | Add your Glean MCP server |
+
+The Codex IDE extension doesn't support plugins. To add your Glean MCP server
+there, use its URL (`[server-url]/mcp/[server-name]`, available from your
+[Glean admin](https://app.glean.com/admin/about-glean)):
+
+```bash
+codex mcp add glean --url [server-url]/mcp/[server-name]
+codex mcp login glean
+```
+
+{{> glean-readme-local-server}}
 
 ## Setup
 
@@ -14,34 +39,30 @@ codex plugin add glean@glean-codex-plugins
 
 ### 2. Set up Glean
 
-Start a new Codex task and prompt the harness: `Set up Glean for me`. Complete
-the browser OAuth flow when prompted, then start a new task so both the bundled
-skills and Glean MCP tools are available.
+Start a new Codex task and ask: `Set up Glean for me`. Enter your work email
+when asked, then finish signing in in your browser. Start a new task so both
+the bundled skills and Glean tools are available.
 
 ## What's Included
 
 The plugin ships a library of skills that auto-trigger by task — there's no
 per-skill install. They cover:
 
-- **Enterprise search & knowledge** — find documents, Slack messages, and email; vet results for freshness and authority.
-- **Code across repos** — explore implementations, find usage examples and similar code, identify code owners, and gather architectural context.
-- **People & org** — find experts by contribution, and identify stakeholders for a change or project.
-- **Meetings** — prep for upcoming meetings and catch up on what you missed.
-- **Onboarding & projects** — ramp up on a team or area, read quick project status, and generate comprehensive project handoffs.
-- **Personal productivity** — summarize your own activity, prep status updates, and surface what needs your attention.
-- **Skill authoring** — discover automation opportunities and generate new skills.
+{{> glean-readme-skills}}
 
 ## Requirements
 
 - [Codex](https://developers.openai.com/codex) with plugin support
+- [Node.js](https://nodejs.org) 22 or later
 - A Glean account with MCP access
 
-## Support
+## Privacy
 
-- [Glean MCP Documentation](https://docs.glean.com/mcp)
-- [Glean Support](https://help.glean.com)
-- [GitHub Issues](https://github.com/gleanwork/agent-plugins/issues)
+The plugin connects only to Glean:
 
-## License
+- During setup, it sends your work email to `app.glean.com` to find your Glean
+  instance.
+- Requests to your Glean instance include the plugin and Codex versions.
+- Sign-in tokens and caches stay on your computer, in `~/.glean`.
 
-MIT — see [LICENSE](LICENSE) for details.
+{{> glean-readme-support}}
@@ -17,8 +17,8 @@ codex plugin add glean@glean-codex-plugins
 codex plugin add glean-dev-docs@glean-codex-plugins
 ```
 
-Start Codex and prompt the harness to set up Glean, for example: `Set up Glean
-for me`. Complete the browser OAuth flow when prompted.
+Start Codex and ask: `Set up Glean for me`. Enter your work email when asked,
+then finish signing in in your browser.
 
 The **Glean developer docs** plugin uses a separate public MCP server. If you
 installed that plugin, add it before starting a new Codex task:
@@ -36,6 +36,7 @@ Then start a new Codex task so the bundled skills and MCP tools are available.
 ## Requirements
 
 - [Codex](https://developers.openai.com/codex) with plugin support
+- [Node.js](https://nodejs.org) 22 or later
 - A Glean account with MCP access (for the `glean` plugin)
 
 ## Support

@@ -1,7 +1,27 @@
 # Glean for Cursor
 
-Official Glean plugin for [Cursor](https://cursor.com) — enterprise search, code exploration,
-and people discovery directly in your development workflow.
+Official Glean plugin for [Cursor](https://cursor.com). Search your company's
+knowledge, explore code across repos, find people and experts, and prepare for
+meetings, right in your editor.
+
+## Where it works
+
+The plugin has two parts:
+
+- **Skills, agents and rules** that Cursor loads from the plugin.
+- **Glean tools** from a local MCP server that the plugin starts.
+
+| Surface                        | Skills            | Glean tools                     |
+| ------------------------------ | ----------------- | ------------------------------- |
+| Cursor editor and Agent Window | Yes               | Yes, from the plugin            |
+| Cursor CLI                     | Not supported yet | Add your Glean MCP server       |
+| Cursor Cloud Agents            | Not supported yet | Add your Glean MCP server       |
+
+To add your Glean MCP server, put its URL (`[server-url]/mcp/[server-name]`,
+available from your [Glean admin](https://app.glean.com/admin/about-glean)) in
+Cursor's MCP settings.
+
+{{> glean-readme-local-server}}
 
 ## Setup
 
@@ -11,38 +31,29 @@ Install from the [Cursor marketplace](https://cursor.com/marketplace/glean).
 
 ### 2. Set up Glean
 
-Start Cursor and prompt the harness to set up Glean, for example: `Set up
-Glean for me`. Complete the browser OAuth flow when prompted, then return to
-Cursor.
+Ask the agent: `Set up Glean for me`. Enter your work email when asked, then
+finish signing in in your browser.
 
 ## What's Included
 
 The plugin ships a library of skills (plus supporting agents and rules) that
 auto-trigger by task — there's no per-skill install. They cover:
 
-- **Enterprise search & knowledge** — find documents, Slack messages, and email; vet results for freshness and authority.
-- **Code across repos** — explore implementations, find usage examples and similar code, identify code owners, and gather architectural context.
-- **People & org** — find experts by contribution, and identify stakeholders for a change or project.
-- **Meetings** — prep for upcoming meetings and catch up on what you missed.
-- **Onboarding & projects** — ramp up on a team or area, read quick project status, and generate comprehensive project handoffs.
-- **Personal productivity** — summarize your own activity, prep status updates, and surface what needs your attention.
-- **Skill authoring** — discover automation opportunities and generate new skills.
-
-The plugin provides a local Glean MCP server. If no Glean tools are visible,
-ask the user to set up Glean by prompting the harness (for example, `Set up
-Glean for me`).
+{{> glean-readme-skills}}
 
 ## Requirements
 
 - [Cursor](https://cursor.com) (latest version)
+- [Node.js](https://nodejs.org) 22 or later
 - A Glean account with MCP access
 
-## Support
+## Privacy
 
-- [Glean MCP Documentation](https://docs.glean.com/mcp)
-- [Glean Support](https://help.glean.com)
-- [GitHub Issues](https://github.com/gleanwork/agent-plugins/issues)
+The plugin connects only to Glean:
 
-## License
+- During setup, it sends your work email to `app.glean.com` to find your Glean
+  instance.
+- Requests to your Glean instance include the plugin and Cursor versions.
+- Sign-in tokens and caches stay on your computer, in `~/.glean`.
 
-MIT — see [LICENSE](LICENSE) for details.
+{{> glean-readme-support}}
@@ -8,19 +8,12 @@
 Official Glean plugins for [Cursor](https://cursor.com) — enterprise knowledge,
 search, code exploration, and people discovery, right in your editor.
 
-## What's new in v3.0.0
-
-- The **`glean`** plugin is refreshed with the latest consolidated skills and
-  agents (search, code exploration, people, meetings, onboarding, productivity).
-  Your existing `glean` install updates in place — no migration needed.
-- A new **`glean-dev-docs`** plugin searches Glean's public developer
-  documentation (APIs, SDKs, MCP) — install it if you build *with* Glean.
-
 ## Install
 
 Add the **`gleanwork/cursor-plugins`** marketplace in Cursor, then install the
 **`glean`** plugin (and **`glean-dev-docs`** if you build with Glean). Once
-installed, ask Cursor to "set up Glean" and complete the browser OAuth flow.
+installed, ask Cursor to `Set up Glean for me`, enter your work email, and
+finish signing in in your browser.
 
 ## Plugins
 
@@ -29,6 +22,12 @@ installed, ask Cursor to "set up Glean" and complete the browser OAuth flow.
 | **[glean](glean)** | Enterprise knowledge — search docs/Slack/email, cross-repo code exploration, people & experts, meetings, onboarding, productivity. |
 | **[glean-dev-docs](glean-dev-docs)** | Search Glean's public developer documentation — APIs, SDKs, MCP, and integration guides. |
 
+## Requirements
+
+- [Cursor](https://cursor.com) (latest version)
+- [Node.js](https://nodejs.org) 22 or later
+- A Glean account with MCP access (for the `glean` plugin)
+
 ## License
 
 MIT License - see [LICENSE](LICENSE) for details.
@@ -0,0 +1,5 @@
+### Why a local server?
+
+Glean asks you to approve tools that change data, such as sending a message or
+creating a ticket. Hosts on MCP versions before 2026-07-28 can't show Glean's
+prompt, so the plugin's local server shows it instead.
@@ -0,0 +1,7 @@
+- **Enterprise search & knowledge** — find documents, Slack messages, and email; vet results for freshness and authority.
+- **Code across repos** — explore implementations, find usage examples and similar code, identify code owners, and gather architectural context.
+- **People & org** — find experts by contribution, and identify stakeholders for a change or project.
+- **Meetings** — prep for upcoming meetings and catch up on what you missed.
+- **Onboarding & projects** — ramp up on a team or area, read quick project status, and generate comprehensive project handoffs.
+- **Personal productivity** — summarize your own activity, prep status updates, and surface what needs your attention.
+- **Skill authoring** — discover automation opportunities and generate new skills.
@@ -0,0 +1,9 @@
+## Support
+
+- [Glean MCP Documentation](https://docs.glean.com/mcp)
+- [Glean Support](https://help.glean.com)
+- [GitHub Issues](https://github.com/gleanwork/agent-plugins/issues)
+
+## License
+
+MIT — see [LICENSE](LICENSE) for details.
@@ -7,6 +7,8 @@ const gleanPluginDescription =
 export default defineConfig({
   name: "glean-plugins",
   version: pkg.version,
+  // Shared README text, included with {{> name}} tags.
+  source: { partials: "partials" },
   metadata: {
     author: {
       name: "Glean",

@@ -1,6 +1,6 @@
 # Glean Developer Docs
 
-Search the public [Glean developer documentation](https://docs.glean.com) — APIs, SDKs,
+Search the public [Glean developer documentation](https://developers.glean.com) — APIs, SDKs,
 MCP, authentication, indexing, and integration guides for building *with* Glean.
 
 This is a separate, focused plugin for people building on the Glean platform. For
@@ -14,8 +14,22 @@ Install from your host's plugin marketplace (Claude Code or Cursor).
 
 ### 2. Configure the Glean Dev Docs MCP server
 
-This plugin uses the public Glean Developer Docs MCP server. See your host's MCP
-setup to add it; no Glean account is required.
+This plugin uses the public Glean Developer Docs MCP server. No Glean account is
+required. In Claude Code, add it with:
+
+```bash
+claude mcp add --transport http glean-dev-docs https://developers.glean.com/mcp
+```
+
+In Cursor, add it to `~/.cursor/mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "glean-dev-docs": { "url": "https://developers.glean.com/mcp" }
+  }
+}
+```
 
 ## What's Included
 
@@ -25,7 +39,7 @@ It searches the public developer documentation and returns cited answers.
 
 ## Support
 
-- [Glean Developer Documentation](https://docs.glean.com)
+- [Glean Developer Documentation](https://developers.glean.com)
 - [GitHub Issues](https://github.com/gleanwork/agent-plugins/issues)
 
 ## License