# MCP server for cloud infrastructure

Clanker Cloud gives MCP-capable agents a local way to ask grounded questions about cloud and Kubernetes infrastructure from the app runtime. The agent connects locally instead of guessing from repository files or using a hosted privileged bridge.

## Use the app runtime first

```text
Open Clanker Cloud
Connect or select local provider context
Ask a grounded app query before giving an agent broader MCP access
```

## Open-source CLI launchers

```bash
clanker mcp --transport stdio
```

For localhost HTTP clients that need the same local runtime through HTTP:

```bash
clanker mcp --transport http
```

Example MCP server config shape:

```json
{
    "mcpServers": {
        "clanker": {
            "command": "clanker",
            "args": ["mcp", "--transport", "stdio"]
        }
    }
}
```

## Agent queries

- Kubernetes troubleshooting: why is checkout returning 502 in prod?
- AWS investigation: what changed around the cost spike this week?
- Cloudflare and edge: which public routes reach EKS and bypass auth?
- Review before apply: draft the safest plan to add private storage for uploads.

## Safety boundary

MCP gives agents a local tool surface through the same runtime that powers the app, but high-impact infrastructure writes still belong behind reviewed plans and explicit approval.

## Related pages

- [Claude Code MCP with Kubernetes](https://clankercloud.ai/examples/claude-code-mcp-kubernetes)
- [Local credentials in Clanker Cloud](https://clankercloud.ai/security/local-credentials)
- [MCP command reference](https://docs.clankercloud.ai/cli/commands/mcp)