Cursor

Context7 brings up-to-date library documentation directly into Cursor. Instead of getting outdated code examples from training data, you get current documentation from source repositories.

Installation#

Run the setup command to configure Context7 for Cursor:

npx ctx7 setup --cursor

Authenticates via OAuth, generates an API key, and installs the appropriate skill. You can choose between CLI or MCP mode.

For manual MCP installation or other configuration options, see All MCP Clients.

Setting Up Rules#

With ctx7 setup, a skill is installed that triggers Context7 automatically. If you prefer to use a rule instead, add one in Cursor.

Cursor Settings.cursorrules File

1

Open Settings

Go to Cursor → Settings... → Cursor Settings → Rules and Commands. You can also press Cmd+Shift+P (or Ctrl+Shift+P on Windows/Linux) and type "Cursor Settings".

2

Add the Rule

Always use Context7 MCP when I ask about library documentation,API references, or need code examples from external packages.

Using Context7#

Add "use context7" to your prompts to fetch current documentation:

use context7 to show me how to set up middleware in Next.js 15use context7 for Prisma query examples with relationsuse context7 for the Supabase syntax for row-level security

If you know the library ID, use it directly to skip resolution:

use context7 with /supabase/supabase for authentication docsuse context7 with /vercel/next.js for app router setup

Cursor Cloud Agents#

Cursor Cloud Agents use MCP servers configured for the cloud agent, not the MCP configuration from your local Cursor installation. If Context7 works in the IDE but a Cloud Agent reports an anonymous quota, add an authenticated HTTP server in the Cloud Agent UI.

Before you begin#

Create an API key in the Context7 dashboard. Keep the key available while you complete the steps below, but do not commit it to your repository or include it in screenshots.

Add Context7 to Cursor Cloud Agents#

1

Open a Cloud Agent

Go to cursor.com/agents and start a new agent. If you start the agent from the Cursor desktop app, select Cloud from the environment menu below the agent input.

2

Open the MCP server menu

Select + (Add context and tools), then MCP Servers and Add MCP.

3

Choose Custom MCP

In the MCP browser, select Custom MCP.

4

Configure the authenticated Context7 server

Enter the following values:

Field	Value
Name	context7-api-key
Type	URL
Server URL	https://mcp.context7.com/mcp
Header key	Context7-API-Key
Header value	Your Context7 API key

The distinct context7-api-key name avoids a namespace collision when the OAuth-based Context7 plugin is also installed. If you do not use the plugin, you can name the server context7.

Context7 also accepts Authorization: Bearer YOUR_API_KEY, as shown in the general MCP client examples. This guide uses Context7-API-Key because that configuration was verified with Cursor Cloud Agents and keeps API-key authentication separate from the plugin's OAuth connection.

Warning

Use a hyphenated header name in Cursor Cloud. Header names containing underscores, such as CONTEXT7_API_KEY, can be dropped by Cursor's proxy. CONTEXT7_API_KEY remains the environment variable name for local stdio connections.

Alternatively, select Edit JSON and use this configuration:

{  "mcpServers": {    "context7-api-key": {      "url": "https://mcp.context7.com/mcp",      "headers": {        "Context7-API-Key": "YOUR_CONTEXT7_API_KEY"      }    }  }}

5

Add and enable the server

Select Add MCP. Before starting the run, open + → MCP Servers again and confirm that context7-api-key is enabled.

A green status confirms that Cursor initialized the MCP server. It does not by itself prove that the request was authenticated.

6

Verify authenticated access

Start a new Cloud Agent run and test both tools:

Use Context7 to resolve the library ID for Next.js, then query its documentationfor middleware. Tell me which Context7 tools you called.

To verify authentication conclusively, query a private library that belongs to the Context7 account associated with the API key:

Use Context7 to query <YOUR_PRIVATE_LIBRARY_ID>. Summarize its installation docs.

If the private library can be read, the Cloud Agent is using the API key. If the agent reports Monthly quota exceeded even though the key has quota, the request is reaching Context7 anonymously; recheck the header name and start a new run after saving the MCP server.

After the API-key header is applied, the same Cloud Agent should be able to resolve a library and return documentation without the anonymous quota error:

OAuth and the Context7 Cursor plugin#

The Context7 plugin uses the OAuth endpoint and does not currently provide a field for an API key. Cursor supports OAuth for Cloud MCP servers, but installing or enabling the plugin does not guarantee that its OAuth sign-in flow has completed.

• Use the plugin when you want OAuth and complete the sign-in prompt for the same Cursor account that launches the Cloud Agent.
• Use the custom HTTP setup above when you need explicit API-key authentication, including access to private Context7 libraries.

See Cursor's documentation for custom MCP servers and Cloud Agent MCP support.

Troubleshooting#

Tips#

# GoodHow do I handle file uploads with the Supabase Storage API?# Less specificHow does Supabase storage work?