Ploi Cloud

io.github.ploicloudPublished by GitHub account ploicloudv1.0.0Updated Oct 24, 2026

European cloud hosting. Deploy and manage apps with your favorite AI coding assistant.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

A remote MCP endpoint for Ploi Cloud, a European cloud hosting service, letting an AI assistant deploy and manage apps.

What you can do
Ploi Cloud is a European cloud hosting platform. This remote MCP server connects an AI coding assistant to it so the assistant can deploy and manage applications hosted there. The manifest lists no individual tools, so the exact operations available are not documented in the supplied material.
When to use it
Consider it if you host applications on Ploi Cloud and want an AI coding assistant to help deploy and manage them from within your workflow. It is not useful if you do not already use Ploi Cloud hosting.
Requirements
A remote streamable HTTP endpoint at ploi.cloud; no local package or runtime is needed. Authentication is OAuth and is required, so you need a Ploi Cloud account and must complete the OAuth authorization flow. Network access to the endpoint is required.
Before you install
The server requires OAuth authorization to your Ploi Cloud account, which may give the assistant access to deploy and manage your hosted applications. Because no tools are listed, review what the connection is permitted to do before authorizing it. Actions taken through it can affect live hosting.

Installation

In SourceWeft

  1. Open Ploi 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/io.github.ploicloud%2Fploi-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": {
    "ploi-cloud": {
      "type": "http",
      "url": "https://ploi.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.