MemScope vs Cursor Team Rules and project rules
Cursor rules give Cursor’s agent standing instructions. MemScope gives every agent a shared memory with per-person access.
What Cursor rules are
Cursor has Project Rules (files in .cursor/rules, version-controlled with the repository), User Rules (your personal preferences across projects) and Team Rules, which Team and Enterprise plan administrators create and manage from the Cursor dashboard and can mark as required. Cursor also supports AGENTS.md as a plain-markdown alternative. Rules are good for applying standards across an organization’s Cursor users.
Side by side
Per-person access
Cursor Team Rules
Team Rules apply to all team members; Project Rules apply to the codebase; User Rules are personal. Per-person or per-group targeting is not documented; rules are scoped by file pattern.
MemScope
Yes. Each person’s agent recalls only memories that person is permitted to see; a deterministic policy decides.
Works across different AI tools
Cursor Team Rules
Cursor supports AGENTS.md. Whether other tools read .cursor/rules: not documented.
MemScope
Yes. Claude Code, Cursor, ChatGPT and other MCP clients share one memory.
Sensitivity levels
Cursor Team Rules
Not documented.
MemScope
Four levels: Public, Internal, Restricted, Highly restricted. Higher levels need more access.
Audit trail
Cursor Team Rules
Project Rules are version-controlled in git. An audit trail for Team Rules: not documented.
MemScope
Yes. Every change is audited.
Who writes the content
Cursor Team Rules
Team administrators create Team Rules in the dashboard; Project Rules are edited in the repository; each user manages their own User Rules.
MemScope
People and their agents save explicit memories; AI only suggests labels.
Cost
Cursor Team Rules
Team Rules need a Team or Enterprise plan. Project Rules live in your repository.
MemScope
$15 per connected user per month after a 60-day trial with 3 connected users.
Statements about Cursor Team Rules come from Cursor docs: Rules, checked November 2026. “Not documented” means those docs do not say. Products change; check the source. https://cursor.com/docs/context/rules
When Cursor Team Rules are enough
- Everyone on the team uses Cursor and the guidance is an organization-wide standard that every member should receive.
- You want an administrator to require a rule, which Team Rules support.
- Project Rules in the repository cover conventions that anyone with the code may read.
In these cases Cursor’s rules are enough. MemScope does not replace them.
When you need MemScope
- Some knowledge is for one team or project, and should not reach everyone who can read the repository.
- Developers use different AI tools and you want one memory they all read and write.
- You need each change to who can see a memory recorded in an audit log.
Documentation checked November 2026.