Mengi Cloud

cloud.mengiPublished by mengi.cloudOfficial publisherv1.0.0Updated Oct 24, 2026

Manage Kubernetes clusters, deployments, databases, secrets and observability on Mengi Cloud.

VerifiedStreamable HTTPWeb executableDatabasesCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for Mengi Cloud that lets an assistant manage Kubernetes clusters, deployments, databases, secrets and observability.

What you can do
  • Manage Kubernetes clusters and deployments
  • Work with databases hosted on Mengi Cloud
  • Handle secrets
  • Inspect observability and monitoring data
  • No tool list is published, so exact actions are not documented
When to use it
Useful when your infrastructure runs on Mengi Cloud and you want an assistant to inspect or operate clusters, deployments, databases, secrets and monitoring from one connection instead of switching consoles.
Requirements
A remote streamable HTTP endpoint at mcp.mengi.cloud; no local package or runtime needed. Authentication is OAuth and required, so a Mengi Cloud account with access to the relevant resources is needed. Network access to the endpoint.
Before you install
The server can manage clusters, deployments, databases and secrets, so an assistant may change or delete live infrastructure and read sensitive secret values. Grant only the OAuth scopes and account permissions you intend the assistant to use, and review write actions before approving them. No tool list is published, so verify capabilities before relying on it.

Installation

In SourceWeft

  1. Open Mengi Cloud in the dashboard and add it to a workspace.
  2. Connect the required 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/cloud.mengi%2Fmengi-cloud/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "mengi-cloud": {
      "type": "http",
      "url": "https://mcp.mengi.cloud/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.