# MCP server for cloud infrastructure Q&A

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.

## What is the setup entry point?

The current setup page is https://clankercloud.ai/mcp.

Agents should fetch the single onboarding endpoint directly:

```bash
curl -fsS "https://clankercloud.ai/agent-onboarding"
```

## What should agents do locally?

Ask the user to open Clanker Cloud, then discover the active app port:

```bash
for p in 8080 8081 8082 8083 8084; do
  curl -fsS "http://127.0.0.1:$p/mcp/instructions" && break
done
```

## 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

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