Overwriting global user config to create self-contained project environment

Hey!

Is it possible to overwrite the entire user config and settings (MCPs, rules, …) in favor of a project config? Currently it appears as though project configs are being merged with global configs? It would be incredibly useful from a reproducibility standpoint to share or distribute a completely self-contained cursor project.

Thank you!

Flemming

Hey, yes you can, you can place the mcp.json file in the root of the .cursor folder of your project. You can also put your rules in .cursor/rules, or use .cursorrules in the root of your project. Additionally, you can place your custom commands in .cursor/commands. This should be enough so that, for example, other team members can use the same configuration.

1 Like

Thanks a lot for the detailed answer. Just to clarify one point: I understand one can add project-specific environment setup through the channels you described above. But as I understand these are merged with what is written in the global config (rules, MCPs, …). Is that correct? At least that is what I am seeing on my end but I might be doing something incorrectly.

Yes, MCP will be merged, and we might be able to improve that. But rules won’t, they’re stored locally in each project.

1 Like

ah that’s great clarification and will help me a lot. Thank you! FWIW, I think it would be quite nice to be able to isolate MCP configs as well. Sometimes multiple MCPs don’t play well with eachother.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.