Krutrim Cloud MCP Server
Use Krutrim Cloud from VS Code, Cursor, Claude Desktop, Claude Code, or Codex. The local stdio server provides 159 tools for discovery and controlled operations across compute, networking, storage, Kubernetes, KPods, Sandboxes, and IAM.
Install
Recommended: uvx
Run the pinned package without installing it into your current Python environment:
uvx krutrim-mcp-server@1.0.5 --version
Python virtual environment
python3 -m venv .venv
source .venv/bin/activate
python -m pip install krutrim-mcp-server==1.0.5
python -m krutrim_mcp_server --version
On Windows, activate with .venv\Scripts\activate.
Connect locally
Create a key in Krutrim Cloud Console → Administration → API keys → Create API Key.
Configure KRUTRIM_API_KEY with the raw key, without a Bearer prefix or surrounding
spaces. Keep keys private and restart the MCP client after changing the key.
Create an API key with curl or Postman
Use POST https://cloud.olakrutrim.com/iam/v1/apikey with an authorized Cloud
Console access token. This token is for key creation only; MCP uses the resulting
API key, not the Console token.
With KRUTRIM_CONSOLE_ACCESS_TOKEN set privately:
curl --request POST 'https://cloud.olakrutrim.com/iam/v1/apikey' \
--header "Authorization: Bearer ${KRUTRIM_CONSOLE_ACCESS_TOKEN}" \
--header 'Content-Type: application/json' \
--header 'x-region: In-Hyderabad-1' \
--data '{"apiKeyName":"mcp-key"}'
In Postman, import this curl request, set Authorization → Bearer Token to your
Console access token, and send the JSON body. Browser cookies are not needed.
Store the returned secretKey securely and use it as KRUTRIM_API_KEY.
VS Code
Use .vscode/mcp.json; the masked prompt keeps the key out of the file:
{
"servers": {
"krutrim-cloud": {
"type": "stdio",
"command": "uvx",
"args": ["krutrim-mcp-server@1.0.5"],
"env": {
"KRUTRIM_API_KEY": "${input:krutrim-api-key}"
}
}
},
"inputs": [
{
"id": "krutrim-api-key",
"type": "promptString",
"description": "Krutrim Cloud API key",
"password": true
}
]
}
Cursor or Claude Desktop
Use your client's private MCP configuration:
{
"mcpServers": {
"krutrim-cloud": {
"command": "uvx",
"args": ["krutrim-mcp-server@1.0.5"],
"env": {
"KRUTRIM_API_KEY": "YOUR_KRUTRIM_API_KEY"
}
}
}
}
Codex
Add this to your private ~/.codex/config.toml:
[mcp_servers.krutrim-cloud]
enabled = true
command = "uvx"
args = ["krutrim-mcp-server@1.0.5"]
[mcp_servers.krutrim-cloud.env]
KRUTRIM_API_KEY = "YOUR_KRUTRIM_API_KEY"
For a virtual environment or local checkout, replace command with the absolute
path to .venv/bin/python and args with ["-m", "krutrim_mcp_server"].
On Windows, use .venv\Scripts\python.exe. No environment-cleanup wrapper is needed.
Use the tools
List resources, select exact identifiers and a supported region
(In-Bangalore-1 or In-Hyderabad-1), then confirm changes. Examples:
List my VPCs in In-Bangalore-1.
List IAM users.
Show Sandbox flavors and templates before creating a Sandbox.
| Goal | Start with |
|---|---|
| Create a VPC | list_vpcs, then create_vpc |
| Create a VM | list_vpcs, list_subnets, and list_compute_flavors |
| Allocate a floating IP | describe_vpc, then create_floating_ip |
| Create a KPod | list_kpod_flavors and list_kpod_templates |
| Create a Sandbox | list_sandbox_flavors and list_sandbox_templates |
| Manage storage | list_volumes, list_volume_types, or list_buckets |
| Manage IAM | list_iam_users, list_iam_groups, and list_iam_roles |
Mutations require confirm=true. Floating-IP allocation also requires
allow_public_ip=true. Set KRUTRIM_MCP_READ_ONLY=true to block mutations.
After a create timeout, check for the resource before retrying; new VMs can take
several minutes to appear in listings.
Verify
With the API key configured privately:
uvx krutrim-mcp-server@1.0.5 --list-tools
uvx krutrim-mcp-server@1.0.5 --doctor
--doctor checks local configuration, not Cloud authentication. Use a read-only
Cloud tool such as list_vpcs to verify access.
User guide
See the user guide for configuration details, safety controls, and troubleshooting.
Encrypted storage access-key delivery
create_storage_access_key returns an encrypted bundle, not a plaintext secret.
Generate a recipient key with krutrim-mcp-credentials init, then follow
Encrypted credential delivery to decrypt
it on your device. Never share the private key or decrypted output.
Metadata
Release files for krutrim-mcp-server 1.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| krutrim_mcp_server-1.0.6.tar.gz | 180.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| krutrim_mcp_server-1.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 306.1 kB
Release files / krutrim_mcp_server-1.0.6.tar.gz
| Download URL | krutrim_mcp_server-1.0.6.tar.gz |
|---|---|
| Size | 180.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7af434d78ee17c6fdccce74f1b98ccde74efae3f1abc8e01b1ac0babce570a7d
|
|
BLAKE2b-256 checksum How to use checksums |
434faf22c4f0e830c3a96a9df05d7046e43aa74b7f8d07b8851538a3f23092e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / krutrim_mcp_server-1.0.6-py3-none-any.whl
| Download URL | krutrim_mcp_server-1.0.6-py3-none-any.whl |
|---|---|
| Size | 125.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fcecdb36250bd7867e65ddb8d2eb25459fa1cd2be82040a23f9380e4f8cdbf3d
|
|
BLAKE2b-256 checksum How to use checksums |
af5906345ead53e117c6e97a67cd536ebd2749d1bd6db0bb79aa66ae3971cb5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logSecurity for krutrim-mcp-server 1.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for krutrim_mcp_server-1.0.6.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.