If your Claude-powered agent needs to spin up cloud infrastructure without hardcoding provider logic, this gives you a single API to query compute, storage, and database options across AWS, GCP, and Azure. It returns normalized JSON with instance specs, cost estimates, and ready-to-run Terraform HCL or CLI commands. Built-in guardrails validate budget caps and region policies before execution, and every call logs to an audit trail. Useful when you're building agents that provision their own infrastructure or need to compare cloud options programmatically without maintaining separate SDKs for each provider. The streamable HTTP transport means you can integrate it directly into your MCP-enabled workflows.
The MCP connector for Synlake — B2AI infrastructure for autonomous agents. Synlake normalizes AWS, GCP, and Azure into one schema, generates ready-to-run execution kits (Terraform HCL + CLI), and prices them before deploy — so an AI agent can discover, evaluate, and provision cloud infrastructure with zero human intervention.
This repository is the open-source MCP server (a thin stdio ↔ HTTP proxy). The infrastructure intelligence — cross-cloud normalization, the cost engine, and execution-kit generation — runs as a hosted service at api.synlake.ai.
🌐 synlake.ai · 📖 Docs · 🔌 MCP: ai.synlake/synlake
A coding agent needs a Kubernetes node pool. It doesn't open a cloud console, compare pricing pages, or hand-write Terraform. It asks Synlake, and gets back a deployable answer:
Agent → Synlake: "compute, 4 vCPUs, 16 GB RAM, us-east-1, budget $100/mo"
Synlake → Agent: best: gcp · e2-standard-4 · $97.82/mo (19.5% cheaper than the priciest)
also: aws t3.xlarge $121.47 · azure Standard_B4ms $121.18
kit: { terraform: "resource \"google_compute_instance\"…",
cli: "gcloud compute instances create…" }
✓ validated: no public ingress, encryption on, within budget
The agent reviews the kit, applies the Terraform, and moves on. Every response is dense, deterministic JSON — built for machine consumption, not dashboards. Synlake tools are read-only: they recommend, price, and validate. A human (or the agent's own policy) runs the execution kit.
flowchart LR
A[AI Agent] -- MCP / REST --> B[Synlake API]
B --> C[Normalizer]
C --> D1[AWS adapter]
C --> D2[Azure adapter]
C --> D3[GCP adapter]
C --> E[Ranking engine<br/>cost + constraints]
E --> F[Execution-kit generator<br/>Terraform + CLI]
F --> G[Guardrails & validation<br/>budget · region · security]
G --> H[Audit log]
H --> A
An agent sends an intent. Synlake normalizes options across clouds, ranks them by cost and constraints, generates a deploy-ready execution kit, runs guardrail checks, logs the call, and returns one machine-ready payload. This repo ships the open-source MCP connector (the AI Agent ↔ Synlake API edge); the boxes to the right of Synlake API run as the hosted service.
Point any MCP client at the hosted server — three lines, nothing to install:
{
"mcpServers": {
"synlake": {
"url": "https://api.synlake.ai/api/mcp",
"headers": { "Authorization": "Bearer sk_synlake_YOUR_KEY" }
}
}
}
For clients that speak stdio (e.g. Claude Desktop), run the npm wrapper — it proxies to the same hosted server:
{
"mcpServers": {
"synlake": {
"command": "npx",
"args": ["-y", "@synlake-ai/mcp-server"],
"env": { "SYNLAKE_API_KEY": "sk_synlake_YOUR_KEY" }
}
}
}
Get a free API key at synlake.ai (100 calls/month, no card required). The estimate endpoint is even callable without a key — zero friction to try.
| Tool | REST endpoint | Description |
|---|---|---|
synlake_query | POST /v1/infrastructure/query | Full recommendation + execution kit (Terraform + CLI) |
synlake_estimate | POST /v1/infrastructure/estimate | Cross-cloud cost comparison — no API key required |
synlake_validate | POST /v1/execution/validate | Dry-run an execution kit (security + budget checks) |
synlake_providers | GET /v1/providers | List supported providers and services |
synlake_usage | GET /v1/agent/usage | Your usage, costs, and spending cap |
Full reference (OpenAPI 3.1, rendered): synlake.ai/docs. Local copy: docs/openapi.yaml. Machine-readable summary for agents: synlake.ai/llms.txt.
| Approach | Multi-cloud | Agent-ready JSON | Execution kit | Cost guardrails | Audit trail |
|---|---|---|---|---|---|
| DIY Terraform | Manual | No | You write it | No | No |
| Pulumi / Crossplane | Yes | No | Partial | No | Partial |
| Cloud provider SDKs | Single | Partial | No | No | Partial |
| Agent frameworks | Via tools | Partial | No | No | No |
| Synlake | 3 clouds | 100% | Full kit | Built-in | Every call |
Wire Synlake as an mcp_toolset — the agent gets all five tools natively, your key stays in an Anthropic vault:
{
"type": "mcp_toolset",
"name": "synlake",
"server": {
"url": "https://api.synlake.ai/api/mcp",
"authorization_token": { "vault_secret": "synlake_api_key" }
}
}
See the MCP quickstart for the Managed Agents API, ant CLI, and Agent SDK flows.
npm install
npm run build # tsc → dist/ (pure proxy)
SYNLAKE_API_KEY=sk_synlake_... node dist/bin.js
SYNLAKE_API_URL overrides the remote endpoint (default https://api.synlake.ai/api/mcp).
Pay per call. No subscriptions, no commitments. Free tier: 100 calls/month, no card required.
| Call type | Price |
|---|---|
| Estimate | $0.01 (free, no key, IP rate-limited) |
| Query (basic) | $0.05 |
| Query (full + Terraform) | $0.10 |
| Validate | $0.05 |
ai.synlake/synlake — registry.modelcontextprotocol.ioThe MCP connector in this repository is MIT licensed (see LICENSE). The Synlake service (api.synlake.ai) — the cost engine, cross-cloud normalization, and execution-kit generation — is proprietary.
El conector MCP de este repo es MIT. El servicio Synlake (api.synlake.ai) es propietario.
© Synlake, LLC — admin@synlake.ai
silenceper/mcp-k8s
azure/containerization-assist
io.github.evozim/aws-builder
reza-gholizade/k8s-mcp-server
flux159/mcp-server-kubernetes