# Claude Code MCP infrastructure context with Clanker Cloud

Use Clanker Cloud when Claude Code or another MCP-capable agent needs live cloud and Kubernetes context instead of guessing from repository files alone.

## Buyer query

Can Clanker Cloud give my coding agent live infrastructure context through MCP without moving credentials to a hosted bridge?

## App workflow

Run Clanker Cloud on the machine with the trusted kubeconfig and cloud credentials, connect the agent to local MCP, then ask:

```text
Why are prod-api pods CrashLoopBackOff, and what cluster evidence supports the answer?
```

## Required context

- Clanker Cloud app or local Clanker runtime, kubeconfig, cloud provider credentials, and an MCP-capable agent.

## Example output

```text
Agent answer: prod-api pods are CrashLoopBackOff after commit 4f2c1b because the container expects REDIS_URL but the live secret still exposes REDIS_HOST and REDIS_PORT. No cluster write was run. Suggested next step: update the app config or generate a reviewed secret migration plan.
```

## Safety boundary

MCP runs locally through the same runtime that powers the app. Apply-style changes still require an explicit approved plan.

## Related

- Full example: https://clankercloud.ai/examples/claude-code-mcp-kubernetes
- MCP product page: https://clankercloud.ai/mcp
- Local credentials: https://clankercloud.ai/security/local-credentials