How does Brief work with Cursor?

Brief connects to Cursor via MCP (Model Context Protocol). When you're coding, Cursor can query Brief for product decisions, customer context, and strategic constraints. It takes about 2 minutes to set up.

What's the difference between cursorrules and Brief?

Cursorrules is a static file that loads at session start. It's good for basic conventions but doesn't remember past decisions or understand your business. Brief provides dynamic context that includes decision history, customer personas, and product strategy.

Cursor Integration

Cursor + Brief

Q: Does Brief slow down Cursor?

No. Context loads in the background. Cursor stays fast and responsive.

Give Cursor real product context. Stop re-explaining your tech stack, business decisions, and customer needs every session.

The Cursorrules Limitation

Cursor's .cursorrules file is a good start. You define your tech stack, coding conventions, and preferences. But it's static text that loads once and knows nothing about your business.

Capability	.cursorrules alone	Cursor + Brief
Coding conventions	✓ Static rules	✓ Dynamic + decisions
Tech stack preferences	✓ You write them	✓ Auto-detected
Past decisions	✗ No memory	✓ Full history
Customer context	✗ Unknown	✓ Personas, needs
Strategic constraints	✗ Not available	✓ Goals, priorities
Session memory	✗ Resets each time	✓ Persists

What Cursor Can Do With Brief

Check Past Decisions

"I'm about to implement auth. Are there any existing decisions about this?"

Cursor queries Brief and finds: "We decided to use Clerk for authentication (Decision BRI-42). Rationale: avoid building auth from scratch, get SSO support."

Understand User Context

"Who are we building this feature for?"

Cursor fetches personas from Brief: "Primary persona: Product Founders. They care about velocity and need strategic clarity."

Validate Approach

"I'm planning to refactor to GraphQL. Does this conflict with anything?"

Cursor runs guard_approach: "Potential conflict: We decided to stick with REST for simplicity (BRI-56)."

Record Decisions

"We're using Postgres instead of MongoDB for relational data needs."

Cursor logs to Brief: "Decision BRI-89 recorded. Would you like to add tags or link to a feature?"

Connect Brief to Cursor

Takes about 2 minutes. No npm packages to install.

Step 1: Add MCP Config

Create or edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "brief": {
      "type": "sse",
      "url": "https://app.briefhq.ai/api/mcp/sse"
    }
  }
}

Step 2: Restart Cursor

Close and reopen Cursor. A browser window will open for authentication.

Step 3: Verify Connection

Go to Settings → Features → MCP Servers. Status should be green.

Full Setup Guide with Troubleshooting →

Frequently Asked Questions

Does Brief slow down Cursor?

No. Context loads in the background while you code. Cursor stays fast and responsive.

Can I use both cursorrules and Brief?

Yes. Keep your .cursorrules for coding conventions. Brief adds dynamic context on top: decisions, customers, strategy. They complement each other.

What data does Brief send to Cursor?

Only what Cursor asks for. When you're coding, Cursor can query Brief for relevant decisions, personas, and constraints. Brief doesn't push data; Cursor pulls what it needs.

How does Brief get my product context?

Brief integrates with your existing tools: Linear, Notion, Slack, Jira, etc. It reads your tickets, docs, and messages to extract product decisions automatically. You can also add context manually.

Give Cursor the Context It Needs

Cursorrules tells Cursor how to code. Brief tells it why. Connect them for AI coding that understands your product.

Get Started with Brief Compare All Tools