How do you share context and team rules across a team in Cursor?

Short answer

Share explicit instructions through repository files or Team Rules, and tools through Team MCP servers. For learned context, Multiplayer Projects share a Project store among members; Teams and Enterprise also support shared chat transcripts. Personal preferences stay separate unless you deliberately publish or copy them into a shared place.

What is shared and what is not

Not everything your Cursor knows, your teammate’s Cursor knows too. It helps to put the places side by side:

Place Shared with the team? How
Project Rules (.cursor/rules/*.mdc) Yes Through version control, with the code
AGENTS.md Yes Through version control; other AI tools read it too
Skills in .cursor/skills/ Yes Through version control
Team Rules Yes Dashboard, managed by team admins
Team MCP servers Yes, once installed Dashboard and team marketplace
Multiplayer Projects Yes, for project members A shared Project store that agents add to
User Rules No Your own account
Skills in ~/.cursor/skills/ Not by themselves Sync to your own Cloud Agents once enabled; share through the team marketplace or the repository
Chat transcripts Shareable on Teams and Enterprise Share a transcript link; recipients can fork the conversation

1. Rules in the repository

The simplest route: put agreements in Project Rules or AGENTS.md and commit them. Whoever clones the repository has them. This works on every plan. How to create a rule and pick a type is in How do you use Cursor rules.

2. Team Rules in the dashboard

Team Rules apply to everyone on the team, whatever repository is open. They exist only on Team and Enterprise plans and are managed by team admins in the Cursor dashboard.

  1. Open the Cursor dashboard as a team admin and go to Team Rules.
  2. Write the rule as free text. Add globs if you want; without a glob it applies to every conversation.
  3. Decide whether to enforce it. An enforced rule is required for everyone and cannot be disabled in Customize. A non-enforced rule can be turned off by users.
  4. Check “Enable this rule immediately” to make it active right away, or leave it as a draft.

When guidance conflicts, the earlier source wins in the order Team Rules, Project Rules, User Rules. So keep Team Rules for what truly holds everywhere: security, language, things that must never happen. Project-specific agreements belong in the repository.

3. Shared tools through MCP

MCP connects Cursor to other systems. A project can have a .cursor/mcp.json in the repository, so everyone gets the same configuration. For servers that serve several users, use SSE or Streamable HTTP with OAuth instead of a local stdio server.

Team admins set up Team MCP servers under Dashboard > Plugins & MCPs. Those are available to Cloud Agents. To also get them in the editor, the Agent Window, and the CLI, choose Add to Team Marketplace; teammates then install the server themselves from Customize. Only team admins can edit a Team MCP server. On Enterprise, admins can use an allowlist to control which MCP servers users may run.

4. Learned context in Projects

Besides rules you write yourself, Cursor has Projects. A Multiplayer Project keeps a Project store that agents add to while they work, and every member of the project uses the same store. It needs a team account and Cursor 3.26.13 or later. A single conversation you share as a transcript link: a teammate can fork it and continue, but it does not become a rule for the whole team.

The common mistake: sharing is not installing

Many teams assume an admin can switch something on for everyone with one click. For Team Rules that is true, if you enforce them. For MCP it is not: putting a server in the team marketplace does not install it for everyone, and an allowlist approves a configuration but distributes nothing. Check per teammate that the server actually runs.

What falls outside

What Cursor shares, it shares with Cursor. If part of the team works in Claude Code, ChatGPT, or Copilot, those tools do not see your Team Rules or dashboard MCP. The only thing several tools read is what sits in the repository: AGENTS.md and skills in .claude/skills/, which Cursor also loads. And knowledge that is not in code (customer agreements, decisions, email) ends up in none of these places by itself. More in How to give AI agents your company context.

Where Bombos fits

Team Rules and Team MCP share context inside Cursor. Bombos is a plugin that does it across all of a team’s AI tools: Cursor, Claude Code, ChatGPT, Copilot, Grok, Codex, and your own agents get one shared memory with team knowledge, learned rules, and what already sits in email, documents, and repos, traceable, in the cloud or on your own server. One developer can try it first before the team joins.

Related questions

Can a user turn off a Team Rule?

Only if the admin does not enforce it. An enforced Team Rule is required for all team members and cannot be disabled in Customize.

What wins when a Team Rule and a Project Rule conflict?

The order is Team Rules, then Project Rules, then User Rules. All are merged; when guidance conflicts, the earlier source wins.

Are my personal skills shared with my team?

Not by themselves. Enable Sync Skills for Cloud Agents to sync personal skills privately to your own Cloud Agents. To share them with teammates, commit them to .cursor/skills/ in the repository or publish them to the team marketplace.

Does an MCP allowlist install the server for everyone?

No. On Enterprise an allowlist controls which MCP servers users may run, but it does not distribute or install them.

Sources

  1. Cursor docs: Rules
  2. Cursor docs: Model Context Protocol (MCP)
  3. Cursor docs: Agent Skills
  4. Cursor docs: Projects
  5. Cursor help: Shared transcripts
The first half hour · free

What does your AI forget?

  1. 01You tell us which AI you use and where it keeps starting over.
  2. 02We show what a shared memory changes there, on your own examples.
  3. 03You keep the plan, with or without Bombos.
Piet Baudoin
Piet BaudoinYou talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe
We reply the same working day.