mcpField
S
Synlake — Cloud Infrastructure for AI Agents

Synlake — Cloud Infrastructure for AI Agents

Remote
synlake.aiCloud & Infra0Updated 20w ago

About Synlake — Cloud Infrastructure for AI Agents

Synlake is an MCP server for comparing, estimating, and preparing cloud infrastructure across AWS, GCP, and Azure. It normalizes options and generates Terraform and CLI execution kits; its tools recommend, price, and validate plans but do not deploy them.

Key features

  1. 01Compare AWS, GCP, and Azure in one schema
  2. 02Rank options by cost and constraints
  3. 03Generate Terraform and CLI execution kits
  4. 04Check security and budget guardrails
  5. 05List providers and supported services
  6. 06View usage and spending caps

Use cases

  1. 01Select a compute instance for an agent
  2. 02Compare cloud costs before deployment
  3. 03Check an execution kit against security and budget rules
  4. 04Find supported cloud providers and services

MCP support

The MCP server gives clients tools for infrastructure queries, cross-cloud estimates, execution-kit validation, provider listings, and usage checks. Clients can connect to the hosted Streamable HTTP endpoint or use the stdio proxy to reach the same service.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.synlake.ai/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://api.synlake.ai/mcpAuth required

Tools

Details

From the project README

Synlake MCP Server

npm MCP Registry License: MIT

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


An agent deploys infrastructure — no human in the loop

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.

Architecture

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.

Quickstart

Hosted (recommended) — MCP over Streamable HTTP

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" }
    }
  }
}
Local stdio wrapper (this package)

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.

Tools

ToolREST endpointDescription
synlake_queryPOST /v1/infrastructure/queryFull recommendation + execution kit (Terraform + CLI)
synlake_estimatePOST /v1/infrastructure/estimateCross-cloud cost comparison — no API key required
synlake_validatePOST /v1/execution/validateDry-run an execution kit (security + budget checks)
synlake_providersGET /v1/providersList supported providers and services
synlake_usageGET /v1/agent/usageYour 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.

Why Synlake

ApproachMulti-cloudAgent-ready JSONExecution kitCost guardrailsAudit trail
DIY TerraformManualNoYou write itNoNo
Pulumi / CrossplaneYesNoPartialNoPartial
Cloud provider SDKsSinglePartialNoNoPartial
Agent frameworksVia toolsPartialNoNoNo
Synlake3 clouds100%Full kitBuilt-inEvery call

Use it from a Claude Managed Agent

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.

Build from source

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).

Pricing

Pay per call. No subscriptions, no commitments. Free tier: 100 calls/month, no card required.

Call typePrice
Estimate$0.01 (free, no key, IP rate-limited)
Query (basic)$0.05
Query (full + Terraform)$0.10
Validate$0.05

Links

License

The 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 — [email protected]

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.