Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Unofficial MCP Server for Scaleway Serverless Functions
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"scaleway-functions": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/cyclimse/mcp-scaleway-functions:0.3.4"
]
}
}
}在终端中运行这条命令
claude mcp add scaleway-functions -- docker run -i --rm docker.io/cyclimse/mcp-scaleway-functions:0.3.4粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"scaleway-functions": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/cyclimse/mcp-scaleway-functions:0.3.4"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"scaleway-functions": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/cyclimse/mcp-scaleway-functions:0.3.4"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 cyclimse 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.3.4)于7个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Signoff
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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 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. |
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).
Running tests:
go tool gotestsum --format testdox
Generating mocks:
go tool mockery