MCP Scaleway Functions
Manage Scaleway Serverless Functions from your agent—list, deploy, and tune functions without living in the Scaleway console.
Overview
io.github.cyclimse/mcp-scaleway-functions is a MCP server for the Operate phase that exposes Scaleway Serverless Functions management to your agent via a Docker OCI stdio package.
What is this MCP server?
- Unofficial MCP server for Scaleway Serverless Functions (community-maintained)
- Distributed as OCI image docker.io/cyclimse/mcp-scaleway-functions:0.3.4 with stdio transport
- Lets agents invoke Scaleway function operations from MCP instead of manual console steps
- GitHub repository cyclimse/mcp-scaleway-functions (registry id 1061220206)
- Version 0.3.4 published as OCI identifier docker.io/cyclimse/mcp-scaleway-functions:0.3.4
- Transport: stdio; registryType oci per MCP server schema
- GitHub repository: github.com/cyclimse/mcp-scaleway-functions (repository id 1061220206)
Community signal: 6 GitHub stars.
What problem does it solve?
You run serverless on Scaleway but every agent question about functions forces you out of the repo into the console or scattered CLI notes.
Who is it for?
Solo builders already on Scaleway Serverless Functions who want MCP-driven deploy and ops checks from Claude Code or Cursor.
Skip if: Teams on AWS Lambda-only stacks, or anyone who require official Scaleway-supported tooling with an enterprise SLA.
What do I get? / Deliverables
After you run the OCI MCP image with valid Scaleway credentials, your agent can drive Serverless Functions operations from the same session as your code.
- Containerized MCP server connected to Scaleway Serverless Functions APIs
- Agent-invokable function management tools for day-two ops
- Repeatable v0.3.4 image pin for team MCP configs
Recommended MCP Servers
Journey fit
Operating serverless workloads on Scaleway is ongoing infra work after you ship, which fits Operate more than first-time UI prototyping. Infra is correct because the MCP server targets cloud function lifecycle on Scaleway, not generic frontend or SEO tasks.
How it compares
Unofficial Scaleway Functions MCP container, not the Scaleway CLI skill bundle or a generic Terraform deploy skill.
Common Questions / FAQ
Who is io.github.cyclimse/mcp-scaleway-functions for?
Developers operating workloads on Scaleway Serverless Functions who use MCP agents and want function lifecycle actions without constant console context switching.
When should I use io.github.cyclimse/mcp-scaleway-functions?
Use it during Operate and infra iteration when you deploy, inspect, or adjust Scaleway functions and want the agent to call MCP tools against your project.
How do I add io.github.cyclimse/mcp-scaleway-functions to my agent?
Pull and run the OCI package docker.io/cyclimse/mcp-scaleway-functions:0.3.4 with stdio transport in your MCP client, injecting Scaleway API credentials per the GitHub project instructions.