菜单
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 当前能够提供的文件。
基于 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.