Connect VS Code

Connect Krutrim Cloud MCP to Visual Studio Code with protected token prompts.

Connect Krutrim Cloud MCP to Visual Studio Code with a local stdio server. Use your VS Code user profile so tokens are not stored in a project or source control.

Before you begin

• Visual Studio Code with chat and MCP support, with uvx available on your local path.

• An active Krutrim Cloud account and an IAM access token plus refresh token from the same sign-in session.

• Complete MFA first if your account requires it.

1. Open the user MCP configuration

In the Command Palette, run MCP: Open User Configuration. This opens the mcp.json file for your VS Code user profile. Keep credentials out of workspace configuration and source control.

2. Add the Krutrim Cloud server

Add this entry, preserving any servers and inputs already in the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "krutrim-access-token",
      "description": "Krutrim Cloud IAM access token",
      "password": true
    },
    {
      "type": "promptString",
      "id": "krutrim-refresh-token",
      "description": "Krutrim Cloud IAM refresh token",
      "password": true
    }
  ],
  "servers": {
    "krutrimCloud": {
      "type": "stdio",
      "command": "uvx",
      "args": ["krutrim-mcp-server"],
      "env": {
        "KRUTRIM_ACCESS_TOKEN": "${input:krutrim-access-token}",
        "KRUTRIM_REFRESH_TOKEN": "${input:krutrim-refresh-token}"
      }
    }
  }
}

VS Code prompts for each token when the server first starts and stores the values securely. Never commit the tokens or paste them into a shared workspace file.

3. Start and verify

Save mcp.json, then run MCP: List Servers from the Command Palette. Start krutrimCloud and review the server configuration before trusting it. In Agent mode, start with a read-only request such as: List my VPCs in In-Bangalore-1.

Troubleshooting

If the server does not start, run uvx krutrim-mcp-server --doctor in a terminal. Use MCP: List Servers to inspect server status and output, then verify the token prompts, IAM permissions, and region.