Exoscale MCP Server

io.github.samisouabniPublished by GitHub account samisouabniv1.0.4Updated Oct 24, 2026

MCP server for managing Exoscale cloud infrastructure — compute, Kubernetes, DNS, databases, storage

VerifiedSTDIODesktop onlyCloud & Infrastructure

Overview

AI-generated overview

Local MCP server that lets an assistant manage Exoscale cloud infrastructure: compute, Kubernetes, DNS, databases and storage.

What you can do
  • Manage Exoscale compute resources such as instances
  • Operate Kubernetes clusters on Exoscale
  • Handle DNS records and zones
  • Work with managed databases and storage
  • No tool list is published, so the exact operations available are not documented in the supplied material.
When to use it
Worth adding when you run workloads on Exoscale and want an assistant to inspect or administer that infrastructure from a chat session instead of the web console or CLI.
Requirements
Runs as a local process on the user's machine, installed from the npm package @samisouabni/exoscale-mcp over stdio; desktop client only. No authentication, environment variables or headers are declared, so how Exoscale credentials are supplied is not documented here.
Before you install
The server is described as managing cloud infrastructure, which typically means creating, changing and deleting billable resources; no tool list is published, so the scope of write actions is unknown. No credentials are declared, so check how API keys are passed before installing. Actions may incur Exoscale charges.

Installation

In SourceWeft

  1. Open Exoscale MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.4LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.