Connect Cursor

Connect Krutrim Cloud MCP to Cursor using a local stdio server. The configuration can be global for your user or scoped to a single repository.

Before you begin

• Complete package installation, sign-in, MFA (if needed), and token handling in the shared Overview.

• Ensure uvx is available in the environment from which Cursor launches its MCP server.

• Keep your IAM access token and refresh token private.

1. Choose the configuration scope

Scope	File	When to use it
Project	.cursor/mcp.json	The server is only for the current repository. Do not commit this file if it contains credentials.
Global	~/.cursor/mcp.json	The server is available to your local Cursor user across projects.

Security note: Cursor starts a local command-based server with the environment values in this file. Store the file only on a trusted machine and avoid committing secret-bearing configuration.

2. Add the server configuration

Create or merge the selected mcp.json file with this entry.

{
  "mcpServers": {
    "krutrim-cloud": {
      "command": "uvx",
      "args": ["krutrim-mcp-server"],
      "env": {
        "KRUTRIM_ACCESS_TOKEN": "YOUR_IAM_ACCESS_TOKEN",
        "KRUTRIM_REFRESH_TOKEN": "YOUR_IAM_REFRESH_TOKEN"
      }
    }
  }
}

3. Reload Cursor and check the server

Reload the Cursor window or restart Cursor. Open Customize → MCPs to confirm that krutrim-cloud starts successfully. If an enterprise policy manages MCP servers, ask your administrator to allow the exact uvx krutrim-mcp-server command.

4. Verify with a read-only request

Run these local checks first:

uvx krutrim-mcp-server --doctor
uvx krutrim-mcp-server --list-tools

Then ask Cursor:

List my VPCs in In-Hyderabad-1.

Review the proposed tool invocation and allow only the read-only request. If the server is unavailable, check the configuration file path, confirm that uvx is on Cursor's executable path, and restart the application.

Use Cloud tools safely

Use the safe operating workflow for any mutating request. Always list resources first, review identifiers and region, then request confirmation before a change.

For the current Cursor MCP configuration reference, see Cursor's MCP documentation.