GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Compare, estimate, and deploy cloud infrastructure across AWS, GCP, and Azure for AI agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http synlake-ai https://api.synlake.ai/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"synlake-ai": {
"url": "https://api.synlake.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"synlake-ai": {
"type": "http",
"url": "https://api.synlake.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Synlake-ai, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 cost + constraints] E --> F[Execution-kit generator Terraform + CLI] F --> G[Guardrails & validation 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](https://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](https://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