Cursor productive in 30 minutes: install, pick Claude Sonnet 4.6, create .cursorrules, install MCP servers. Here's the exact setup.
Step 1: Install (2 minutes)
Download from cursor.com. It's a VS Code fork — open your existing project and your extensions and settings transfer.
Sign in with your Anysphere account ($20/mo Pro recommended).
Step 2: Pick your default model (1 minute)
Cmd/Ctrl + Shift + P → "Cursor: Settings" → Models.
Recommended defaults:
- Agent mode: Claude Sonnet 4.6 with extended thinking
- Composer: Claude Sonnet 4.6
- Inline edits: Claude Sonnet 4.6 (or GPT-5 for very long contexts)
Tab completion uses Cursor Tab automatically — no model selection needed.
Step 3: Create .cursorrules (10 minutes)
In your repo root, create .cursorrules:
# Project conventions
## Tech stack
- Next.js 15 App Router + React 19
- TypeScript strict mode
- Tailwind 3.4
- Supabase Postgres + Drizzle ORM
## Coding style
- Single quotes for strings
- 2-space indentation
- Prefer functional components and hooks
- Server components by default; client components only when needed
## Testing
- Vitest for unit tests
- Playwright for e2e
- No snapshot tests — explicit assertions only
## Avoid
- jQuery, lodash (use native methods)
- Legacy class components
- Default exports for utilities
Update when your conventions evolve.
Step 4: Install MCP servers (10 minutes)
Three high-value MCP servers to install first:
1. GitHub — read repos, PRs, issues 2. Linear — read tickets, create issues 3. Filesystem — already built-in, no install needed
Cursor settings → MCP → Add Server. Paste the config from each tool's docs.
For more options see Best MCP servers in 2026.
Step 5: Learn the three core modes (5 minutes)
Inline chat (Cmd/Ctrl + L) For quick questions about code. "What does this function do?" "Why is this failing?"
Composer (Cmd/Ctrl + I) For changes that span 2-10 files. Plan-then-execute pattern.
Agent mode (Cmd/Ctrl + K → Agent) For longer autonomous loops. Refactors, feature implementations, debugging across files.
The 3 patterns that make Cursor pay back fastest
Pattern 1: Chat-then-Compose. Use inline chat to think through a change. Then move to Composer to execute.
Pattern 2: Cursor Tab everywhere. Trust the tab completion. It's the single biggest productivity gain in Cursor.
Pattern 3: MCP for context. When the agent doesn't know your data, install the relevant MCP server instead of pasting context manually.
Three Cursor mistakes to avoid
1. Over-prompting in agent mode. Long detailed prompts often produce worse results than concise goals. Let the agent ask clarifying questions.
2. Ignoring .cursorrules. Without it, the agent doesn't know your conventions and you fight it on every PR.
3. Skipping the Composer plan review. Composer proposes a plan before executing. Read it — that's where you catch wrong direction early.
The verdict
Cursor in 30 minutes: install → pick model → write .cursorrules → install MCP servers → learn three modes. After that, it's the single most productive tool in any 2026 engineer's daily stack.
For more see Cursor vs Windsurf, Cursor review, and Best coding agents in 2026.