CursorContext mistakesLevel 3: Workflows

Are Too Many Rules and MCP Servers Hurting Cursor?

They can be. Always-on rules, skill descriptions, MCP catalogs and subagent docs all take up context before you've typed anything. Cursor's course warns that too many rules consume unnecessary context and may confuse the agent. Keep what's always loaded short, and move the rest to where it loads on demand.

Prompt to copy
Audit my always-on context. Read .cursor/rules and AGENTS.md, and list each rule with its type and rough length.

For each one, recommend: keep always on, scope with globs, move to a skill, delete because a linter covers it, or delete because you already do this without being told. Flag any two rules that conflict.

Don't change anything until I've approved your list.
Top: needed always. Bottom: needed sometimes.
Always Apply rulea few lines, every chat
Reference a filean @ file is read only when needed
Glob ruleloads with matching files
Skillfull text loads when relevant
Left: short. Right: long.
Rule of thumb, not a Cursor chart, based on its rules and skills docs: keep only the top-left box always loaded.

Try it now

  1. 1Open a brand-new chat, then click the context ring next to the prompt input. Note the size of **Rules, MCP and Skills**.
  2. 2Open Customize in the sidebar, and turn off an MCP server or rule you haven't needed lately.
  3. 3Open another new chat and check the tray. It worked if the starting usage has dropped and your next task still goes well.

Use it when

When a new chat already looks fairly full before any work begins, when Agent seems to ignore a rule you know exists, or after your team has added rules for months without removing any.

Skip it when

Don't strip a small, working setup down to nothing. A few short rules are worth their cost, since Cursor's course shows just three lines fixing a team's wrong test framework. And don't remove an MCP server the agent uses in most tasks just to save a little space.

Why it works

The context window is fixed, so whatever is loaded every time leaves less for your code and conversation. Cursor's breakdown tray lists Rules, Skills, MCP and Subagents as their own categories, so this cost is visible. Long instructions also compete with each other. A list of 50 points gives the model more chances to overlook the one that matters, and two rules can conflict without you noticing. Glob-scoped rules, skills and subagents are all ways to keep instructions available without loading them each time.

Example

Say your .cursor/rules has a 900-line always-on file. It has a copy of your style guide, which ESLint already enforces, plus deploy steps you use monthly and a few real conventions. You delete the style guide, move the deploy steps to a skill, and split the conventions into a short always-on rule plus two glob rules for src/api and src/components. The window has more room, and the instructions that matter stand out.

Going further

Cursor's guidance is to keep a rule under 500 lines, but that's an upper limit and not a target. Reference a file rather than pasting it, since an @ file in a rule is read only when needed. Team rules without a glob apply to every conversation, and enforced ones can't be turned off, so a long one affects everyone. Admins should treat them as a budget. If you repeat instructions just for review, Bugbot has its own BUGBOT.md files, so those don't need to load in every coding chat.

Common mistakes

  • Adding a rule for each mistake ever made and never removing any.
  • Setting everything to Always Apply because it feels safer.
  • Copying a popular rules file from the internet without checking whether it applies to your repo.
  • Pasting whole templates into rules rather than referencing them by path.

Sources

Checked 6 November 2026. Products change often, so confirm details with the vendor.

Related

Beyond the course