> For the complete documentation index, see [llms.txt](https://docs.cloud.olakrutrim.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloud.olakrutrim.com/mcp/connect-claude-desktop.md).

# Connect Claude Desktop

Connect Krutrim Cloud MCP to Claude Desktop with a local stdio server. Claude Desktop starts the server using your privately configured Krutrim Cloud API key.

## Before you begin

* First, complete the shared installation and API-key setup in the [MCP Overview](/mcp/overview.md). These guides use local stdio, not a hosted OAuth connection.
* Install `uv` so the `uvx` command is available.
* Use the raw API key as `KRUTRIM_API_KEY`, without a `Bearer` prefix or surrounding spaces. Keep it private and restart the client after changing the key.

> **Important:** Do not put credentials in a repository, shared config, prompt, or screenshot. Use only the placeholder values below until you add the configuration on your own device.

## Connect to Krutrim Cloud

{% stepper %}
{% step %}

### Open the local Claude Desktop configuration

Claude Desktop's interface changes over time. For a local command-based MCP server, edit its standard local configuration file:

| Platform | Configuration file                                                |
| -------- | ----------------------------------------------------------------- |
| macOS    | `~/Library/Application Support/Claude/claude_desktop_config.json` |
| Windows  | `%APPDATA%\Claude\claude_desktop_config.json`                     |

If your Claude Desktop version offers an **Extensions** experience, that is intended for packaged desktop extensions. Krutrim Cloud MCP is configured here as a local `stdio` server.
{% endstep %}

{% step %}

### Add the Krutrim Cloud MCP server

Merge this entry with any existing `mcpServers` entries; do not overwrite other servers.

```json
{
  "mcpServers": {
    "krutrim-cloud": {
      "command": "uvx",
      "args": [
        "krutrim-mcp-server"
      ],
      "env": {
        "KRUTRIM_API_KEY": "YOUR_KRUTRIM_API_KEY"
      }
    }
  }
}
```

{% endstep %}

{% step %}

### Restart Claude Desktop

Close and reopen Claude Desktop after saving the file. This starts the local MCP server and loads its available tools.
{% endstep %}

{% step %}

### Verify with a read-only request

Then use a read-only prompt in Claude Desktop:

```
List my VPCs in In-Bangalore-1.
```

Review the proposed tool call and allow only the read-only request.
{% endstep %}
{% endstepper %}

## Next steps

Before changing Cloud resources, follow the safety guidance in the [MCP Overview](/mcp/overview.md). Start with a read-only request and review the exact region and resource identifiers.

Need help? Open [Troubleshooting](/mcp/troubleshooting.md) for startup, API-key, and tool-discovery checks.

Use the safe operating workflow before requesting changes to Cloud resources. For current Claude Desktop product guidance, see [Anthropic's MCP documentation](https://docs.anthropic.com/en/docs/mcp).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cloud.olakrutrim.com/mcp/connect-claude-desktop.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.