agentleFS
context-dot-devcontext-dot-dev/cursor-plugin/skills/connect-context-dev/SKILL.md

connect-context-dev

Skill9 starsChanged 3 months agoMITView on GitHub

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.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use a read-only request:

    line 20
  2. Distinctive:

    Never ask the user to paste an OAuth token or private API key into chat.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Connect Context.dev in Cursor

Standard connection

  1. Open Cursor Settings → Tools & MCP.
  2. Find the context server installed by this plugin and enable it.
  3. Select Connect or Authenticate.
  4. Complete the Context.dev sign-in and consent flow in the browser.
  5. Return to Cursor and confirm that the server lists its tools.

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.

Verify

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 with formats: { markdown: true }. A successful tool call confirms both the MCP connection and the authenticated Context account.

Troubleshooting

SymptomAction
context is missingRefresh or reinstall the plugin, then reload the Cursor window
A second legacy Context.dev server appearsRemove the old manual server and reinstall this plugin
401 or authentication requiredDisconnect the server, reconnect it, and complete OAuth again
Browser flow does not openOpen the server details and select Authenticate manually
Tools remain unavailable after OAuthReload the Cursor window and re-enable the server
Account has insufficient creditsUse get-usage to check the balance and next refill; use get-usage-history for recent consumption; do not repeatedly retry

Never ask the user to paste an OAuth token or private API key into chat.

Direct API development

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.