MCP Scaleway Functions MCP Server

MCP Scaleway Functions MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Scaleway Functions directly instead of describing what you should do. Unofficial MCP Server for Scaleway Serverless Functions.

What you get

Download the latest release from the releases page or build it from source using Go.

What the assistant can call

Once MCP Scaleway Functions is connected, these are the calls the assistant has available:

• create_and_deploy_function_namespace — Create and deploy a new function namespace
• list_function_namespaces — List all function namespaces
• delete_function_namespace — Delete a function namespace
• list_functions — List all functions in a namespace
• list_function_runtimes — List all available function runtimes
• create_and_deploy_function — Create and deploy a new function
• update_function — Update the code or the configuration of an existing function
• delete_function — Delete a function
• download_function — Download the code of a function. This is useful to work on an existing function
• fetch_function_logs — Fetch the logs of a function
• add_dependency — Add a dependency to a local function. Useful for dependencies that rely on native code and therefore need Docker to be installed

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 2 environment variables: SCW_SECRET_KEY, SCW_DEFAULT_REGION. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Scaleway Functions's toolset — create_and_deploy_function_namespace, list_function_namespaces, delete_function_namespace and 8 more — is a fair guide to whether it matches your workflow. It is maintained by cyclimse; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Scaleway Functions's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Scaleway Functions.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp scaleway functions mcp server does with a few real requests.