diff --git a/README.md b/README.md index 41d1cbf..d356af7 100644 --- a/README.md +++ b/README.md @@ -16,13 +16,13 @@ Then configure your Glean MCP connection — add your server to `~/.cursor/mcp.j { "mcpServers": { "glean": { - "url": "https://YOUR-INSTANCE-be.glean.com/mcp/YOUR-SERVER-NAME" + "url": "YOUR-SERVER-URL/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. +Replace `YOUR-SERVER-URL` with your Glean server URL (find it at ) 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 @@ -34,9 +34,9 @@ Replace `YOUR-INSTANCE` with your Glean instance name and `YOUR-SERVER-NAME` wit - [Cursor](https://cursor.com) (latest version) - A Glean account with MCP access -- Your Glean MCP server URL (format: `https://[instance]-be.glean.com/mcp/[server-name]`) +- Your Glean MCP server URL (find it at ) -> **Note:** Glean MCP server URLs are instance-specific and cannot be bundled with the plugin. Your Glean administrator can provide your server name. +> **Note:** Glean MCP server URLs cannot be bundled with the plugin. Your Glean administrator can provide your server name. ## Support diff --git a/glean/README.md b/glean/README.md index a1796af..73a6c02 100644 --- a/glean/README.md +++ b/glean/README.md @@ -19,15 +19,15 @@ Add your server to `~/.cursor/mcp.json`: { "mcpServers": { "glean": { - "url": "https://YOUR-INSTANCE-be.glean.com/mcp/YOUR-SERVER-NAME" + "url": "YOUR-SERVER-URL/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. +Replace `YOUR-SERVER-URL` with your Glean server URL (find it at ) +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. ## What's Included @@ -81,10 +81,9 @@ is handled automatically on first use. - [Cursor](https://cursor.com) (latest version) - A Glean account with MCP access -- Your Glean MCP server URL (format: `https://[instance]-be.glean.com/mcp/[server-name]`) +- Your Glean MCP server URL (find it at ) -> **Note:** Glean MCP server URLs are instance-specific. Your Glean administrator can provide -> your server name. +> **Note:** Your Glean administrator can provide your server name. ## Support diff --git a/glean/commands/mcp-setup.md b/glean/commands/mcp-setup.md index fc23a14..d168afe 100644 --- a/glean/commands/mcp-setup.md +++ b/glean/commands/mcp-setup.md @@ -9,11 +9,9 @@ Help the user configure a Glean MCP server for Cursor. This command can be run m ## Setup Flow -### Step 1: Get Instance Name +### Step 1: Get Server URL -Ask the user for their Glean instance name. Explain that if their Glean URL is `https://acme-be.glean.com`, their instance name is `acme`. - -You can find your Glean URL here: +Ask the user for their Glean server URL. They can find it at . ### Step 2: Get Server Name @@ -27,13 +25,13 @@ Once you have both values, instruct the user to add the following to their `~/.c { "mcpServers": { "glean": { - "url": "https://[instance]-be.glean.com/mcp/[server-name]" + "url": "[server-url]/mcp/[server-name]" } } } ``` -Replace `[instance]` with their instance name and `[server-name]` with the server name. +Replace `[server-url]` with their server URL (e.g. `https://acme-be.glean.com` or `https://be-4f5226e2.glean.com`) and `[server-name]` with the server name. ### Step 4: Confirm Success @@ -46,7 +44,6 @@ After configuration: ## Important Notes -- The URL format is: `https://[instance]-be.glean.com/mcp/[server-name]` -- The `-be` suffix is required (it's the backend endpoint) +- The URL format is: `[server-url]/mcp/[server-name]` - Cursor handles OAuth authentication automatically on first tool use - The MCP configuration file is at `~/.cursor/mcp.json` diff --git a/glean/commands/mcp-status.md b/glean/commands/mcp-status.md index 132ad00..f811ff5 100644 --- a/glean/commands/mcp-status.md +++ b/glean/commands/mcp-status.md @@ -39,7 +39,7 @@ If the user wants to verify the connection is working, suggest they try a simple Glean MCP Status: Configured Servers: - - glean: https://acme-be.glean.com/mcp/default + - glean: https://acme-be.glean.com/mcp/default (your URL may differ) Status: Ready (authentication will be prompted on first use) ``` diff --git a/glean/skills/mcp-setup/SKILL.md b/glean/skills/mcp-setup/SKILL.md index e39822e..8973950 100644 --- a/glean/skills/mcp-setup/SKILL.md +++ b/glean/skills/mcp-setup/SKILL.md @@ -1,7 +1,7 @@ --- name: mcp-setup description: 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. + Use when the user wants to set up Glean in Cursor or add a new MCP server. --- # Glean MCP Server Setup @@ -10,11 +10,9 @@ Help the user configure a Glean MCP server for Cursor. This workflow can be repe ## Setup Flow -### Step 1: Get Instance Name +### Step 1: Get Server URL -Ask the user for their Glean instance name. If their Glean URL is `https://acme-be.glean.com`, their instance name is `acme`. - -You can find your Glean URL here: +Ask the user for their Glean server URL. They can find it at . ### Step 2: Get Server Name @@ -28,13 +26,13 @@ Once you have both values, instruct the user to add the following to their `~/.c { "mcpServers": { "glean": { - "url": "https://[instance]-be.glean.com/mcp/[server-name]" + "url": "[server-url]/mcp/[server-name]" } } } ``` -Replace `[instance]` with their instance name and `[server-name]` with the server name. +Replace `[server-url]` with their server URL (e.g. `https://acme-be.glean.com` or `https://be-4f5226e2.glean.com`) and `[server-name]` with the server name. ### Step 4: Confirm Success @@ -47,7 +45,6 @@ After configuration: ## Important Notes -- The URL format is: `https://[instance]-be.glean.com/mcp/[server-name]` -- The `-be` suffix is required (it's the backend endpoint) +- The URL format is: `[server-url]/mcp/[server-name]` - Cursor handles OAuth authentication automatically on first tool use - The MCP configuration file is at `~/.cursor/mcp.json` diff --git a/glean/skills/mcp-status/SKILL.md b/glean/skills/mcp-status/SKILL.md index bf72581..16984ec 100644 --- a/glean/skills/mcp-status/SKILL.md +++ b/glean/skills/mcp-status/SKILL.md @@ -40,7 +40,7 @@ If the user wants to verify the connection is working, suggest they try a simple Glean MCP Status: Configured Servers: - - glean: https://acme-be.glean.com/mcp/default + - glean: https://acme-be.glean.com/mcp/default (your URL may differ) Status: Ready (authentication will be prompted on first use) ```