docs(mcp): fix Cursor install link on MCP setup page - #1634
Closed
Dhravya wants to merge 1 commit into
Closed
Conversation
…page Co-authored-by: Dhravya Shah <dhravya@supermemory.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-app | 898e28d | Commit Preview URL Branch Preview URL |
Sep 01 2026, 05:49 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-mcp | 898e28d | Sep 01 2026, 05:48 PM |
Member
|
invalid |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
On the MCP Setup and Usage page, the Cursor section's "install option" pointed at the bare
https://app.supermemory.airoot instead of the actual MCP install surface. This updates it to link directly to the MCP setup page where Cursor's one-click install lives:Why
Unauth QA flagged that the doc still tells people to do the Cursor install "in app.supermemory.ai", raising the question of whether it should point to the console / current auth surface instead.
I verified the actual flow in the codebase:
apps/webis the consumer app served at app.supermemory.ai; it links toconsole.supermemory.aionly as the separate "Developer console" for API keys/usage.MCP_CLIENTS→cursor→ "One-click MCP install in Cursor" inintegrations-view.tsx). The canonical route is/integrations/mcp, which is guest-accessible perapps/web/middleware.ts.app.supermemory.ai(apps/mcp/src/server/index.ts), and MCP uses OAuth — no API key, so the console isn't involved.So the app.supermemory.ai flow is still the real one — it should not change to console. The only real defect was the imprecise link (root instead of the MCP install page). This is the minimal correct fix.
Scope
apps/docs/supermemory-mcp/setup.mdx. No rewrite of the MCP docs, no other copy touched.Nothing ships until merge + deploy.