Synlake

ai.synlakePublished by synlake.aiOfficial publisherv0.1.0Updated Oct 26, 2026

Unified API to query AWS, GCP, Azure and generate Terraform/CLI execution kits for AI agents.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

Remote MCP server that lets an assistant query AWS, GCP and Azure through one API and generate Terraform or CLI execution kits.

What you can do
  • Query cloud resources across AWS, GCP and Azure through a single unified API
  • Generate Terraform configurations and CLI execution kits for cloud changes
  • Support AI agents that need to inspect or act on multi-cloud environments
  • No individual tools are listed in the manifest, so exact operations are not documented here
When to use it
Useful when an assistant needs to look across more than one cloud provider without wiring up separate integrations, or when you want it to produce Terraform or CLI steps for cloud work.
Requirements
A remote endpoint at api.synlake.ai over streamable HTTP; no local package or runtime. A bearer token is required in the Authorization header, and the provider states a free key can be obtained through its registration page.
Before you install
The Authorization bearer token is a credential and must be kept private. Generated Terraform or CLI kits may be intended to change cloud infrastructure, so review any plan before applying it. Queries send cloud account details to a third-party service.

Installation

In SourceWeft

  1. Open Synlake in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.synlake%2Fsynlake/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "synlake": {
      "type": "http",
      "url": "https://api.synlake.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Synlake integrations