
Scaleway MCP server
io.github.scalewayPublished by GitHub account scalewayv2.65.1Updated Oct 24, 2026
Scaleway MCP server for interacting with the Scaleway APIs
Overview
Exposes Scaleway CLI commands as MCP tools so an assistant can list and manage Scaleway cloud resources such as servers and IAM users.
- What you can do
- Run Scaleway CLI commands as tools, named namespace_resource_verb (for example instance_server_list).
- List and inspect cloud resources such as compute instances and IAM users.
- Reach any other Scaleway API operation the CLI exposes, since all commands are registered as tools.
- Reuse the CLI's existing configuration and credentials for these calls.
- When to use it
- Useful when you already work with Scaleway cloud resources and want an assistant to query or operate them through the CLI's command set instead of switching to the console.
- Requirements
- A local Scaleway CLI installation (scw) started with the mcp server serve subcommand, or the published container image. Scaleway credentials configured as for the CLI, via the config file at ~/.config/scw/config.yaml or SCW_CONFIG_PATH, or environment variables such as SCW_ACCESS_KEY and SCW_SECRET_KEY. Network access to Scaleway APIs.
Installation
In SourceWeft
- Open Scaleway MCP server in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Follow the launch instructions in the repository.
README
MCP Server for Scaleway CLI
This namespace provides MCP (Model Context Protocol) server functionality, exposing Scaleway CLI commands as AI tools.
Usage
Starting the MCP Server
This starts the MCP server over stdio, which can be connected to by MCP-compatible AI assistants.
Configuration
The MCP server uses the same configuration as the CLI:
- Config file:
~/.config/scw/config.yamlor$SCW_CONFIG_PATH - Environment variables:
SCW_ACCESS_KEY,SCW_SECRET_KEY, etc.
Available Tools
All CLI commands are exposed as MCP tools with the naming convention:
namespace_resource_verb(e.g.,instance_server_list)
Examples:
instance_server_list- List serversiam_user_list- List IAM users
Architecture
server/- Core MCP server implementationserver.go- MCP server wrapper and tool registrationtool.go- Command-to-tool conversion and executionschema.go- JSON Schema generation from ArgSpecs
Development
Testing
Debug Mode
Enable debug logging:
Tool
You can use MCP inspector to explore and test the available tools.
Example: Using with an MCP Client
Configure your MCP client to connect to the Scaleway CLI server:
The client will then have access to all Scaleway CLI commands as tools.
Source: internal/namespaces/mcp/README.md at commit dfd09cb
Tools
0Version history
5- v2.65.1LatestOct 7, 2026
- v2.65.0Oct 7, 2026
- v2.64.0Oct 6, 2026
- v2.63.0Sep 28, 2026
- v2.62.0Sep 16, 2026
Score
50% 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
- License10 pts