메뉴
Connect or troubleshoot Context.dev in Cursor using the production MCP server and OAuth. Use when the user installs this plugin, asks how to authenticate, cannot see Context.dev tools, or receives a 401 from the Context MCP.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/context-dot-dev/cursor-plugin --skill connect-context-dev명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Run and manage large asynchronous Context.dev web jobs. Use when the user needs to scrape many URLs, crawl at scale, process up to 25,000 URLs in one job, avoid synchronous timeouts, inspect batch progress or results, or cancel or delete a previously submitted batch.
Retrieve company brand intelligence and design data with Context.dev. Use when the user asks for a company's logo, colors, fonts, style guide, social profiles, description, industry, address, stock information, brand kit, or lookup by domain, name, email, ticker, ISIN, transaction descriptor, or direct URL.
Discover or read multiple pages from a website with Context.dev. Use when the user asks to map a site, find URLs in a sitemap, crawl documentation or a site section, gather several linked pages, or locate the most relevant pages within one domain.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | connect-context-dev |
| description | Connect or troubleshoot Context.dev in Cursor using the production MCP server and OAuth. Use when the user installs this plugin, asks how to authenticate, cannot see Context.dev tools, or receives a 401 from the Context MCP. |
context server installed by this plugin and enable it.The plugin uses the production Streamable HTTP endpoint at https://mcp.context.dev/mcp. OAuth is discovered from the server automatically. Do not add headers, client secrets, or API keys to mcp.json.
Use a read-only request:
Use Context.dev to scrape https://www.context.dev and return the page title.
The agent should call web-scrape-markdown. A successful tool call confirms both the MCP connection and the authenticated Context account.
| Symptom | Action |
|---|---|
context is missing | Refresh or reinstall the plugin, then reload the Cursor window |
| A second legacy Context.dev server appears | Remove the old manual server and reinstall this plugin |
| 401 or authentication required | Disconnect the server, reconnect it, and complete OAuth again |
| Browser flow does not open | Open the server details and select Authenticate manually |
| Tools remain unavailable after OAuth | Reload the Cursor window and re-enable the server |
| Account has insufficient credits | Review usage in the Context.dev dashboard; do not repeatedly retry |
Never ask the user to paste an OAuth token or private API key into chat.
OAuth covers Cursor's MCP connection. A user only needs an API key when writing their own application against the Context.dev REST API or SDK. In that case, direct them to the Context.dev dashboard and store the key in a server-side CONTEXT_DEV_API_KEY environment variable. Do not place it in this plugin's MCP configuration.