Official Marketplace Context7 plugin ships the Claude Code package (/mcp), not the Cursor plugin (/mcp/oauth)

Support Bug Reports
, ,
1

The official Cursor Marketplace listing for Context7 serves a different plugin than the Cursor-specific plugin in the same upstream repo.

Marketplace listing:

Marketplace: cursor-public
Plugin id: 406
Installed name: context7-plugin

What actually gets installed (from the Cloud Agent / plugin cache manifest):

What the same repo publishes as the Cursor plugin:

  • plugins/cursor/context7/mcp.json
  • URL: mcp.context7.com/mcp/oauth
  • Added in this PR (titled “add Context7 plugin for Cursor marketplace”): upstash/context7#1659
  • That Cursor plugin already existed at the pinned commit above; the marketplace still points at the Claude Code directory.

Impact:

  • Installing “Context7” from the official Marketplace does not use the OAuth endpoint.
  • Cloud Agents cannot complete Context7 login the way the Cursor plugin is documented to work, because the shipped MCP is /mcp rather than /mcp/oauth.

I don’t know whether the publisher submitted the Claude Code path, or Cursor registered the wrong subdirectory from the repo. Either way, the listing does not match plugins/cursor/context7.

Expected:

  • Official Marketplace Context7 should ship plugins/cursor/context7 (OAuth MCP), or the listing should make it explicit that it is the Claude Code plugin and /mcp.

Related existing thread (same Marketplace SHA / API key confusion): “Settings for plugins from cursor marketplace?” (topic 156236)

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

8

Hey @Yusei_Fujimatsu, the Marketplace “Context7” entry currently installs the anonymous https://mcp.context7.com/mcp endpoint rather than the Cursor plugin’s /mcp/oauth, which is why Cloud Agents never prompt you to sign in. This isn’t anything on your end. We’ve let the team know so the listing can be repointed.

To get authenticated Context7 in Cloud Agents today:

  1. On cursor.com/agents, click the + left of the prompt box, hover MCP Servers, and turn off the Context7 plugin if it’s on (avoids a duplicate).
  2. Add MCP → Custom MCP, type HTTP, name context7, URL https://mcp.context7.com/mcp/oauth. Save and click Authorize.
  3. Start a new cloud agent (existing ones won’t pick it up).

Prefer an API key? Use https://mcp.context7.com/mcp and add a CONTEXT7_API_KEY header instead. Same setup works on desktop via ~/.cursor/mcp.json. Docs: Model Context Protocol (MCP) | Cursor Docs

Let me know if the tools don’t show up in a fresh cloud agent.

9

Thanks @mohitjain!

I set up a custom MCP with /mcp/oauth as you described. Cloud Agent custom MCP wasn’t available in the Cursor desktop app, so I configured it from the web UI on cursor.com/agents.

Appreciate the quick help.