GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
Compare, estimate, and deploy cloud infrastructure across AWS, GCP, and Azure for AI agents.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http synlake-ai https://api.synlake.ai/mcp --header 'Authorization: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"synlake-ai": {
"url": "https://api.synlake.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"synlake-ai": {
"type": "http",
"url": "https://api.synlake.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 Synlake-ai 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.2.0)于6个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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