feat(plugins): use harness setup across agent hosts

overrides/claude/root/README.md

@@ -57,8 +57,8 @@ Restart Claude Code if prompted. `glean` carries everything the old plugins did.
 /plugin install glean-dev-docs@glean-plugins
 ```
 
-Then connect a Glean MCP server — ask Claude to "set up Glean" and the `glean`
-plugin's `connect-glean` skill walks you through it. Skills auto-trigger by task.
+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.
 
 ## Plugins
 

overrides/codex/glean/README.md

@@ -12,18 +12,11 @@ codex plugin marketplace add gleanwork/codex-plugins
 codex plugin add glean@glean-codex-plugins
 ```
 
-### 2. Configure your Glean MCP server
+### 2. Set up Glean
 
-Get your server URL and server name from the
-[Glean MCP configurator](https://app.glean.com/settings/install?mcpConfigure=true), then run:
-
-```bash
-codex mcp add glean --url https://YOUR-INSTANCE-be.glean.com/mcp/YOUR-SERVER-NAME
-codex mcp login glean
-```
-
-Complete the browser OAuth flow, then verify with `codex mcp list`. Start a new
-Codex task so both the bundled skills and Glean MCP tools are available.
+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.
 
 ## What's Included
 
@@ -42,7 +35,6 @@ per-skill install. They cover:
 
 - [Codex](https://developers.openai.com/codex) with plugin support
 - A Glean account with MCP access
-- Your Glean MCP server URL and server name
 
 ## Support
 

overrides/codex/glean/skills/skill-creation-guide/SKILL.md

@@ -39,8 +39,8 @@ time, sub-30-second manual tasks, or things the user will forget exist.
 
 When the user asks what they should automate, analyze their work patterns first.
 
-Requires the Glean MCP tools. If they aren't visible, the user hasn't connected
-a Glean MCP server — point them at the **connect-glean** skill.
+Requires the Glean MCP tools. If they aren't visible, ask the user to set up
+Glean by prompting the harness (for example, `Set up Glean for me`).
 
 1. Gather context with Glean: `memory` (roles, responsibilities, active
    projects), `user_activity` (past ~2 weeks), and `search` for process docs

overrides/codex/root/README.md

@@ -17,14 +17,12 @@ codex plugin add glean@glean-codex-plugins
 codex plugin add glean-dev-docs@glean-codex-plugins
 ```
 
-Before starting Codex, connect the MCP server used by the plugin you installed:
-
-- **Glean enterprise knowledge:** get your server URL and name from the
-  [Glean MCP configurator](https://app.glean.com/settings/install?mcpConfigure=true),
-  then run `codex mcp add glean --url <server-url>/mcp/<server-name>` followed by
-  `codex mcp login glean`.
-- **Glean developer docs:** run
-  `codex mcp add glean-dev-docs --url https://developers.glean.com/mcp`.
+Start Codex and prompt the harness to set up Glean, for example: `Set up Glean
+for me`. Complete the browser OAuth flow when prompted.
+
+The **Glean developer docs** plugin uses a separate public MCP server. If you
+installed that plugin, add it before starting a new Codex task:
+`codex mcp add glean-dev-docs --url https://developers.glean.com/mcp`.
 
 Then start a new Codex task so the bundled skills and MCP tools are available.
 

overrides/cursor/root/README.md

@@ -20,8 +20,8 @@ search, code exploration, and people discovery, right in your editor.
 
 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 the `glean` plugin's `connect-glean`
-skill walks you through connecting a Glean MCP server.
+installed, ask Cursor to "set up Glean". If it needs an MCP URL, follow the
+Glean MCP configuration steps in the `glean` plugin README.
 
 ## Plugins
 

shared/glean/README.md

@@ -9,15 +9,11 @@ code exploration, and people discovery directly in your development workflow.
 
 Install from the Claude Code plugin marketplace.
 
-### 2. Configure your Glean MCP server
+### 2. Set up Glean
 
-Add your Glean MCP server (get your server URL from the [Glean MCP configurator](https://app.glean.com/settings/install?mcpConfigure=true)):
-
-```bash
-claude mcp add glean https://YOUR-INSTANCE-be.glean.com/mcp/default --transport http --scope user
-```
-
-Restart Claude Code after adding — OAuth authentication is handled automatically on first use.
+Start Claude Code 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
+Claude Code.
 
 ## What's Included
 
@@ -32,14 +28,14 @@ by task — there's no per-skill install. They cover:
 - **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 tools are used through whatever Glean MCP server is connected in Claude
-Code; if none is configured, see the setup above.
+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`).
 
 ## Requirements
 
 - [Claude Code](https://claude.com/claude-code) (latest version)
 - A Glean account with MCP access
-- Your Glean MCP server URL (get it from the [Glean MCP configurator](https://app.glean.com/settings/install?mcpConfigure=true))
 
 ## Support
 

shared/glean/skills/project-handoff/SKILL.md

@@ -22,8 +22,8 @@ This skill drives the standard Glean MCP tools. If the host exposes the
 a suitable research subagent when subagents are available, or gather the same
 material directly. For the param shape and pitfalls of `search`, `chat`,
 `meeting_lookup`, and `employee_search`, see the using-glean reference at
-`using-glean/reference/`. If no Glean tools are visible, point the user to the
-**connect-glean** skill.
+`using-glean/reference/`. If no Glean tools are visible, ask the user to set up
+Glean by prompting the harness (for example, `Set up Glean for me`).
 
 ## Core Principles
 

shared/glean/skills/skill-creation-guide/SKILL.md

@@ -43,8 +43,8 @@ time, sub-30-second manual tasks, or things the user will forget exist.
 
 When the user asks what they should automate, analyze their work patterns first.
 
-Requires the Glean MCP tools. If they aren't visible, the user hasn't connected
-a Glean MCP server for this host — point them at their host's Glean MCP setup.
+Requires the Glean MCP tools. If they aren't visible, ask the user to set up
+Glean by prompting the harness (for example, `Set up Glean for me`).
 
 1. Gather context with Glean: `memory` (roles, responsibilities, active
    projects), `user_activity` (past ~2 weeks), and `search` for process docs

shared/glean/skills/using-glean/SKILL.md

@@ -13,7 +13,8 @@ The tools listed below come from the user's Glean MCP server connection. Refer t
 
 In the raw MCP tool list, Glean tools appear as `mcp__glean_[server-name]__[tool]` where `[server-name]` is the user's configured server identifier (e.g., `default`, `production`, `acme`). The tool suffix after the final `__` is always consistent across deployments. Use whatever Glean server is visible in your tool inventory.
 
-If no Glean tools are visible, the user hasn't configured a Glean MCP server for this host. Point them at the Glean MCP setup for their host.
+If no Glean tools are visible, ask the user to set up Glean by prompting the
+harness (for example, `Set up Glean for me`).
 
 ## Intent → tool decision tree