Compare, estimate, and deploy cloud infrastructure across AWS, GCP, and Azure for AI agents.
MCPpedia last refreshed this data
io.github.Synlake-ai/mcp-server is an MCP server that compare, estimate, and deploy cloud infrastructure across AWS, GCP, and Azure for AI agents. Its tool list has not been published yet over stdio and http, requires no API key, and scores 79/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"synlake": {
"url": "https://api.synlake.ai/api/mcp",
"headers": {
"Authorization": "Bearer sk_synlake_YOUR_KEY"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Compare, estimate, and deploy cloud infrastructure across AWS, GCP, and Azure for AI agents.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in devops / ai-ml
MCP server for using the GitLab API
A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
An open-source AI agent that brings the power of Gemini directly into your terminal.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Synlake-ai/mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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/execut |