Unofficial MCP Server for Scaleway Serverless Functions
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-cyclimse-mcp-scaleway-functions": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Model Context Protocol (MCP) server to manage and deploy Scaleway Serverless Functions using the Model Context Protocol standard.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud
MCP Server for kubernetes management commands
Static infrastructure analysis via MCP: databases, AWS services, IaC, and code patterns.
Upload, organize, search, and transform images, videos, and files with AI-powered tools.
MCP server for Hostinger API
MCP Security Weekly
Get CVE alerts and security updates for io.github.cyclimse/mcp-scaleway-functions and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Model Context Protocol (MCP) server to manage and deploy Scaleway Serverless Functions using the Model Context Protocol standard.
[!CAUTION] 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.
Download the latest release from the releases page or build it from source using Go.
Run the MCP server:
./mcp-scaleway-functions
By 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:
Add a new server configuration in your .vscode/mcp.json file:
{
"servers": {
"mcp-scaleway-functions": {
"url": "http://localhost:8080",
"type": "http",
}
},
}
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.
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-functions
| Tool | Description |
|---|---|
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 fun |