mcp-scaleway-functions
Provides tools to manage and deploy Scaleway Serverless Functions, including creating and deleting namespaces and functions, updating functions, downloading function code, fetching logs, and adding dependencies.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-scaleway-functionslist my function namespaces"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Scaleway Functions
Model Context Protocol (MCP) server to manage and deploy Scaleway Serverless Functions using the Model Context Protocol standard.
This project is unofficial and not affiliated with or endorsed by Scaleway. Some small safety measures are in place to prevent the LLM from doing destructive actions, but they're not foolproof. Use at your own risk.
Getting Started
Download the latest release from the releases page or build it from source using Go.
Run the MCP server:
./mcp-scaleway-functionsBy default, the MCP server runs with the SSE transport on http://localhost:8080, but you can also change it to use Standard I/O (stdio) transport via the --transport stdio flag.
Then, configure your IDE or tool of choice to connect to the MCP server. Here are some examples:
VSCode (sse example)
Add a new server configuration in your .vscode/mcp.json file:
{
"servers": {
"mcp-scaleway-functions": {
"url": "http://localhost:8080",
"type": "http",
}
},
}Crush (stdio example)
Crush is an open-source coding agent that supports MCP. You can find more information about in the Crush repository.
Add a new server configuration in your ~/.config/crush/crush.json file:
{
"$schema": "https://charm.land/crush.json",
"mcp": {
"scaleway-functions": {
"type": "stdio",
"command": "mcp-scaleway-functions",
"args": ["--transport", "stdio"],
"timeout": 600,
"disabled": false
}
}
}You can even use Crush with Scaleway Generative APIs by adding a new provider in the same ~/.config/crush/crush.json file:
{
"mcp": {
// ... see above ...
},
"providers": {
"scaleway": {
"name": "Scaleway",
"base_url": "https://api.scaleway.ai/v1/",
"type": "openai",
// To fetch from environment variables, use the `$VAR_NAME` syntax.
// Note: this key requires the "GenerativeApisModelAccess" permission.
"api_key": "$SCW_SECRET_KEY",
"models": [
{
"name": "Qwen coder",
"id": "qwen3-coder-30b-a3b-instruct",
"context_window": 128000,
"default_max_tokens": 8000
}
]
}
}
}That's it 🎉! Have fun vibecoding and vibedevoopsing as you please.
Related MCP server: Scaleway MCP Server
Configuration
By default, the MCP server reads from the standard Scaleway configuration file located at ~/.config/scw/config.yaml.
Further configuration can be done via the Scaleway environment variables to configure the MCP server.
For instance, you can set a region to work in via the SCW_DEFAULT_REGION environment variable.
SCW_DEFAULT_REGION=nl-ams ./mcp-scaleway-functionsAvailable Tools
Tool | Description |
| Create and deploy a new function namespace. |
| List all function namespaces. |
| Delete a function namespace. |
| List all functions in a namespace. |
| List all available function runtimes. |
| Create and deploy a new function. |
| Update the code or the configuration of an existing function. |
| Delete a function. |
| Download the code of a function. This is useful to work on an existing function. |
| Fetch the logs of a function. |
| Add a dependency to a local function. Useful for dependencies that rely on native code and therefore need Docker to be installed. |
Debugging
You can enable debug logging by using the --debug flag when starting the MCP server. This will log all requests and responses to/from the Scaleway API.
To configure the log level, use the --log-level flag (default is info). Available log levels are: debug, info, warn, error.
Logs are stored in the $XDG_STATE_HOME/mcp-scaleway-functions directory (usually ~/.local/state/mcp-scaleway-functions).
Development
Running tests:
go tool gotestsum --format testdoxGenerating mocks:
go tool mockeryThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityBmaintenanceMCP server to manage Adila platform via natural language, enabling deploys, logs, metrics, and infrastructure mutations through CLI AI clients.MIT
- AlicenseAqualityDmaintenanceA comprehensive MCP server for managing Scaleway cloud infrastructure, enabling control of instances, databases, storage, networking, and more through natural language.11MIT
- Flicense-qualityDmaintenanceThis MCP server wraps MetaCall FaaS API endpoints as tools, enabling LLMs to list deployments, call functions, and deploy repositories directly via natural language.
- Flicense-qualityDmaintenanceAn MCP server for interacting with Temporal Cloud workflows across multiple regions, providing tools to list, describe, terminate, and retrieve step results from workflows via natural language.1
Related MCP Connectors
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server for interacting with the Supabase platform
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cyclimse/mcp-scaleway-functions'
If you have feedback or need assistance with the MCP directory API, please join our Discord server