RFE: Cursor MCP server installation docs

[cevich]

Description

I was happy to see that the workstation installation guide includes instructions for setting up Cursor. Though sometimes I feel like I'm the only person on the planet that uses Cursor these days.

However the MCP Tools Installation section unfortunately only has eyes for Claude. Since running the local MCP servers is so fundimental to Ymir workstation, would some kind soul please write up some cursor docs?

I think it may be as simple as editing ~/.cursor/mcp.json and following the Claude "Option B" section. But I can't get it to work and setting the DEBUG_FILE envars doesn't help 😢

Benefit

The 1% of the 1% of users utilizing Cursor will feel welcome and supported 😀

Importance

It feels important to me. If I can't figure it out on my own, I will likely give up and abandon all hopes of utilizing Ymir locally. Probably forever 😞

Workaround

• There is an existing workaround that can be used until this feature is implemented.

Participation

• I am willing to submit a pull request for this issue. (Packit team is happy to help!)

[cevich]

If someone wants to write this up, here's a summary of how I got the MCP servers working in Cursor:

I have lots of repos to manage, and don't want a million rhel-config.json files. So I created a ~/.config/ymir directory and placed the file in there.

Then (as is the preferred practice) I made two env files to hold all the environment variables (and secrets) under ~/.local/share/ymir-venv/secrets/ for ymir-privileged-gateway.env and ymir-unprivileged-gateway.env. Contents as per existing docs. Though I did not set any kerberos options, and the gateway successfully obtained tickets via Heim KCM socket and/or keyring (I'm running Fedora 43 CSB).

Lastly, I edited ~/.cursor/mcp.json and set the following content. I'm not sure if ${userHome} is a cusor-specific magic token or not, but it works for me:

{
  "mcpServers": {
    "ymir-privileged": {
      "command": "${userHome}/.local/share/ymir-venv/bin/ymir-privileged-gateway",
      "envFile": "${userHome}/.local/share/ymir-venv/secrets/ymir-privileged-gateway.env",
      "cwd": "${userHome}/.config/ymir"
    },
    "ymir-unprivileged": {
      "command": "${userHome}/.local/share/ymir-venv/bin/ymir-unprivileged-gateway",
      "envFile": "${userHome}/.local/share/ymir-venv/secrets/ymir-unprivileged-gateway.env",
      "cwd": "${userHome}/.config/ymir"
    }
  }
}

Putting this into effect then requires a ctrl-shift-r or "Reload Window" command-pallet (ctrl-shift-p) command. Running /mcp in the agent panel confirms both gateways are connected.