> ## Documentation Index
> Fetch the complete documentation index at: https://docs.context.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Cursor Plugin

> Install Context.dev from the Cursor Marketplace and connect its live-web tools with browser-based OAuth.

The official Context.dev plugin packages the production MCP server with focused skills, commands, and rules for live-web research and API development. It can search, scrape, crawl, extract structured data, parse documents, retrieve brand intelligence, capture screenshots, monitor sites, and run batches.

<Card title="Install Context.dev for Cursor" icon="download" href="https://cursor.com/marketplace/context.dev">
  Open the official Cursor Marketplace listing.
</Card>

## Install and connect

<Steps>
  <Step title="Install the plugin">
    Open the [Context.dev Marketplace listing](https://cursor.com/marketplace/context.dev), select **Install**, and choose a user or project scope.

    You can also run this in Cursor Agent:

    ```text theme={null}
    /add-plugin context-dev
    ```
  </Step>

  <Step title="Enable the MCP server">
    Open **Cursor Settings → Tools & MCP**, find the `context` server installed by the plugin, and enable it.
  </Step>

  <Step title="Authorize Context.dev">
    Select **Connect** or **Authenticate**. Cursor opens Context.dev in your browser. Sign in and approve access, then return to Cursor and confirm that the server lists its tools.
  </Step>

  <Step title="Start a new Agent chat">
    Plugin skills, rules, and commands load into new chats after installation. Open a new chat before testing the integration.
  </Step>
</Steps>

<Info>
  Cursor's interactive Context.dev tools use OAuth. Do not put an API key, bearer token, or custom header in the plugin's `mcp.json`.
</Info>

## Verify the setup

Send a read-only request:

```text theme={null}
Use Context.dev to scrape https://www.context.dev and return the page title and source URL.
```

Cursor should call `web-scrape-markdown`. A successful result confirms that the plugin loaded, the `context` server is enabled, and OAuth completed.

## Use the plugin

Describe the result directly or use one of the bundled commands:

| Command             | Use it for                                        |
| ------------------- | ------------------------------------------------- |
| `/search-web`       | Find current sources when you do not know the URL |
| `/scrape-url`       | Read a known page as clean Markdown               |
| `/extract-web-data` | Return fields shaped by a JSON Schema             |
| `/brand-colors`     | Retrieve a company's detected brand colors        |

Example requests:

```text theme={null}
Use Context.dev to find Stripe's latest official product announcements and cite the source URLs.
```

```text theme={null}
Use Context.dev to extract every open engineering role from this careers site as JSON with title, location, team, and application URL.
```

```text theme={null}
Use Context.dev to retrieve the brand profile for linear.app, including its logo, colors, fonts, and social profiles.
```

<Warning>
  Monitor and batch tools can create or change persistent account state. Ask for create, update, run, cancel, or delete operations explicitly and review the call before approving it.
</Warning>

## Build with the API

OAuth authenticates Cursor's MCP tools. Code that you write to call the Context.dev REST API or SDKs directly uses a separate secret key from the [Context.dev dashboard](https://context.dev/dashboard). Store that key server-side as `CONTEXT_DEV_API_KEY`; never put it in browser code or commit it to source control.

## Troubleshooting

| Symptom                                         | Fix                                                                                                                |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| The `context` server is missing                 | Refresh or reinstall the plugin, then run **Developer: Reload Window**.                                            |
| A second, legacy Context.dev server appears     | Remove the older manual server, then refresh the marketplace plugin.                                               |
| Cursor reports `401` or authentication required | Disconnect `context`, reconnect it, and complete browser authorization again.                                      |
| Tools remain unavailable after OAuth            | Reload the Cursor window, re-enable `context`, and start a new Agent chat.                                         |
| Calls fail for insufficient credits             | Review usage in the [Context.dev dashboard](https://context.dev/dashboard); repeated retries will not add credits. |

## Reference

<CardGroup cols={2}>
  <Card title="Plugin source" icon="github" href="https://github.com/context-dot-dev/cursor-plugin">
    Inspect the manifest, MCP configuration, skills, commands, and rules.
  </Card>

  <Card title="Cursor plugin docs" icon="book" href="https://cursor.com/docs/plugins">
    Installation scopes and plugin management in Cursor.
  </Card>

  <Card title="Context.dev MCP guide" icon="robot" href="/install-mcp">
    Hosted server tools and authentication details.
  </Card>

  <Card title="Context.dev API quickstart" icon="code" href="/quickstart">
    Add Context.dev to application code with an SDK or REST.
  </Card>
</CardGroup>