Is there a way to configure MCP servers on our self hosted agents that we have hosted in k8s. I dont want to configure any dashboards on cursor as i want some self hosted agents to have access to some MCP while others dont. My current setup i am making a rule and then before the agents starts i places that rule in the .cursor skills folder (placing in .cursor/rules folder doesnt get it picked up idk y, sounds like a bug). Then i copy over a config into .cursor/mcp.json, but that doesnt seem to work.
answers my question
Hey, glad you found the answer. That thread covers the main point.
Quick recap for later: cloud agents, including self-hosted, only read MCP from the dashboard at cursor.com/dashboard/integrations. Repo-level .cursor/mcp.json isn’t supported. Per-agent granularity is handled via the toggles when you start a session at cursor.com/agents.
About .cursor/rules not being picked up: that’s not expected. On cloud agents, rules should work (separately from skills). If you want me to dig in, please share:
- The
.cursor/rules/structure in your repo (file names, plus the frontmatter withalwaysApplyanddescription) - How you start the agent (workspace root, commands)
- An example rule file that didn’t get applied
Then I can check what’s failing. It’s either a workspace detection issue in your K8s setup, or a detail with the rule type (always-applied vs agent-requestable).