diff --git a/third_party/front/.cursor-plugin/plugin.json b/third_party/front/.cursor-plugin/plugin.json index 1804e13603..aa4a982a53 100644 --- a/third_party/front/.cursor-plugin/plugin.json +++ b/third_party/front/.cursor-plugin/plugin.json @@ -1,7 +1,7 @@ { "name": "front", "displayName": "Front", - "version": "1.0.0", + "version": "1.1.0", "description": "Search conversations, draft and send replies, and manage tags, tasks, and inboxes.", "author": { "name": "Cursor", @@ -27,24 +27,5 @@ "email", "productivity" ], - "variables": { - "type": "object", - "properties": { - "CLIENT_ID": { - "type": "string", - "title": "Front Client ID", - "description": "Client ID of a Front developer app with the Front MCP feature, from Front Settings → Company → Developer." - }, - "CLIENT_SECRET": { - "type": "string", - "title": "Front Client Secret", - "description": "Client Secret of the same Front developer app." - } - }, - "required": [ - "CLIENT_ID", - "CLIENT_SECRET" - ] - }, "mcpServers": "./mcp.json" } diff --git a/third_party/front/CHANGELOG.md b/third_party/front/CHANGELOG.md index dced792d0d..2430d174ad 100644 --- a/third_party/front/CHANGELOG.md +++ b/third_party/front/CHANGELOG.md @@ -2,6 +2,11 @@ All notable changes to this plugin will be documented here. +## 1.1.0 + +- Dropped the `CLIENT_ID` and `CLIENT_SECRET` plugin variables and the MCP auth values that forwarded them. The connection keeps the `feature:mcp` scope and no longer asks users for Front developer app credentials. +- README: replaced the developer app setup with the install-and-sign-in path. + ## 1.0.0 — initial release - Added the `front` MCP server pointing at Front's hosted Streamable HTTP endpoint (`https://mcp.frontapp.com/mcp`). diff --git a/third_party/front/README.md b/third_party/front/README.md index d07c6aa8b6..3055904120 100644 --- a/third_party/front/README.md +++ b/third_party/front/README.md @@ -6,9 +6,8 @@ Search conversations, read full timelines, draft and send replies, post internal ## Install -1. A Front admin creates a developer app and notes its credentials (see [Setup](#setup)). -2. Open **Cursor Settings → Plugins**, search for **Front**, and click **Install**. -3. Set **Front Client ID** and **Front Client Secret**, then complete the Front sign-in prompt. +1. Open **Cursor Settings → Plugins**, search for **Front**, and click **Install**. +2. Complete the Front sign-in prompt. Or run `/add-plugin front` in chat. @@ -21,8 +20,6 @@ Or run `/add-plugin front` in chat. "type": "http", "url": "https://mcp.frontapp.com/mcp", "auth": { - "CLIENT_ID": "${CLIENT_ID}", - "CLIENT_SECRET": "${CLIENT_SECRET}", "scopes": ["feature:mcp"] } } @@ -30,30 +27,13 @@ Or run `/add-plugin front` in chat. } ``` -Front does not support dynamic client registration, so the connection is a confidential client: a Front admin registers one developer app and Cursor sends that app's client ID and secret. Each user still signs in with their own Front account, and tool calls run with that teammate's Front permissions. +The connection requests Front's `feature:mcp` scope, the value Front documents for clients that need one. Each user signs in with their own Front account, and tool calls run with that teammate's Front permissions. ## Setup -### 1. Create the Front developer app +There is nothing to configure. Install the plugin and complete the Front sign-in prompt. -In Front, go to **Settings → Company → Developer** and create an app (for example "Cursor MCP Connector"): - -1. On the **Features** tab, click **Add feature** and select **Front MCP**. -2. Note the **Client ID** and **Client secret**. -3. Register the redirect URLs Cursor uses: - - | Surface | Redirect URL | - | --- | --- | - | Desktop | `http://localhost:8787/callback` | - | Web and Cloud Agents | `https://www.cursor.com/agents/mcp/oauth/callback` | - | Grok Bot | `https://www.cursor.com/bot/mcp/oauth/callback` | - -4. Under **Resource permissions**, select the narrowest set that covers your use case: `read` for a research agent, `read` + `write` for a drafting copilot, and `send` only if the agent should actually send messages. -5. Save the app. - -### 2. Enter the credentials in Cursor - -In **Dashboard → Plugins → Configure**, set **Front Client ID** and **Front Client Secret** from that app. On a team marketplace an admin sets them once for everyone; each member still completes their own Front sign-in. +A Front admin decides what the connection can reach by choosing **Resource permissions** on the connected app: `read` for a research agent, `read` + `write` for a drafting copilot, and `send` only if the agent should actually send messages. ## What agents can do diff --git a/third_party/front/mcp.json b/third_party/front/mcp.json index 57a14b0a5b..e6a50fd603 100644 --- a/third_party/front/mcp.json +++ b/third_party/front/mcp.json @@ -4,8 +4,6 @@ "type": "http", "url": "https://mcp.frontapp.com/mcp", "auth": { - "CLIENT_ID": "${CLIENT_ID}", - "CLIENT_SECRET": "${CLIENT_SECRET}", "scopes": ["feature:mcp"] } }