IBM Code Engine MCP Server

Name: IBM Code Engine MCP Server
Author: markusvankempen

作者：markusvankempen版本 1.4.2i★ –i在你的电脑上运行

注册名称io.github.markusvankempen/code-engine-mcp-server

安装

概览

作者提供的说明（英文原文）

Deploy to IBM Code Engine from Cursor, Copilot, Claude & Cline. Build, push, deploy via MCP.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 开发者工具
你需要填写：IBMCLOUD_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： IBMCLOUD_API_KEY, IBMCLOUD_REGION, CONTAINER_RUNTIME

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "code-engine": {
      "command": "npx",
      "args": [
        "-y",
        "code-engine-mcp-server"
      ],
      "env": {
        "IBMCLOUD_API_KEY": "your-value",
        "IBMCLOUD_REGION": "your-value",
        "CONTAINER_RUNTIME": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add code-engine --env IBMCLOUD_API_KEY=your-value --env IBMCLOUD_REGION=your-value --env CONTAINER_RUNTIME=your-value -- npx -y code-engine-mcp-server

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "code-engine": {
      "command": "npx",
      "args": [
        "-y",
        "code-engine-mcp-server"
      ],
      "env": {
        "IBMCLOUD_API_KEY": "your-value",
        "IBMCLOUD_REGION": "your-value",
        "CONTAINER_RUNTIME": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "code-engine": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "code-engine-mcp-server"
      ],
      "env": {
        "IBMCLOUD_API_KEY": "your-value",
        "IBMCLOUD_REGION": "your-value",
        "CONTAINER_RUNTIME": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

IBMCLOUD_API_KEY 机密必填 env
IBM Cloud API key used to authenticate and call Code Engine APIs
IBMCLOUD_REGION env
Default IBM Cloud region (for example: us-south)
CONTAINER_RUNTIME env
Optional container runtime override: docker or podman

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 markusvankempen 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 1384 个服务器的 0%
发布到注册中心的时间比此分类中其他 1384 个服务器的 30% 更新
基础检查结果等于或优于此分类中其他 1384 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

IBM Code Engine MCP Server 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：IBMCLOUD_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.4.2）于4个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者：github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT3天前更新

安装

Desktop Commander

作者：wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT15天前更新

安装

Cloudflare MCP

作者：cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

IBM Code Engine MCP Server

MCP server for IBM Code Engine — build, push, and deploy containers from Cursor, Copilot, Claude, and Cline using natural language.

Current release: v1.7.8 — 28 tools instead of 112 (one tool per resource with an action field, same capability, old names still work), a shared local HTTP server for the VS Code extension, a web admin UI with a *Remote client* tab (test tools, logging, users and API keys, events), MCP Remote Config inside VS Code, and a check that the server you point at really is a code-engine MCP server. See CHANGELOG.md and the tool reference.

Search terms: code-engine-mcp · ibm-code-engine · ibm-cloud · ibm-container-registry · mcp-server · model-context-protocol · cursor · github-copilot · claude-desktop · cline · docker · podman · serverless · container-deployment · typescript · npx · ai-agents · devops · cloud-native · watsonx-orchestrate

Author: Markus van Kempen | markus.van.kempen@gmail.com · markusvankempen.github.io *No bug too small, no syntax too weird.*

How It Works

flowchart TD

A([AI Assistant\nCopilot / Claude / Cline / Bob]) -->|MCP JSON-RPC| B[Code Engine MCP Server]

B --> C{Tool Category}

D -->|build / push / validate| E E -->|image reference| F

G -->|proc_build_push_deploy| D G -->|proc_apply_manifest| F

F --> H[(Projects\nApps\nBuilds\nJobs\nSecrets\nDomains)]

H -->|ready| I([Live App\nhttps://app.region.codeengine.appdomain.cloud])

style A fill:#1261FE,color:#fff style B fill:#0f3460,color:#fff style G fill:#7b2d8b,color:#fff style I fill:#198038,color:#fff

✨ What You Get

28 tools, one per resource. ce_app, ce_job, ce_secret, … each take an action (list, get, create, delete, …). Every earlier capability is still there; see the tool reference.
Container workflow tools for Docker or Podman (local_container, dockerfile)
IBM Container Registry (icr) and the whole Code Engine surface: projects, apps, jobs, builds, secrets, config maps, domains, bindings, functions, fleets
Multi-step procedures: build, push and deploy in one call (proc_build_push_deploy), custom domains, declarative manifests
One server, many clients. Run it over stdio, or as an HTTP server that your IDE, assistants, the web UI and the VS Code extension all share
Web admin UI (/admin): overview, activity, users, API keys, runtime settings, and a *Remote client* tab that tests the tools and configures the server (logging, users and keys, events)
MCP-ready setup for GitHub Copilot, Cursor, Cline, Bob, Windsurf, Antigravity, Claude Desktop, and the VS Code extension in vscode-extension/ (including *MCP Remote Config*)
MCP Activity Dashboard — live timeline of tool calls, session grouping, deploy outcome highlights, and a Deployments inventory tab
Live activity logging — optional JSONL event stream for every MCP tool call (MCP_ACTIVITY_* env vars)

🚀 Quick Start

# 1) Install dependencies

npm install

2) Build the server

npm run build

3) Run once to verify

node build/index.js

Then configure your MCP client using one of the examples in the Configuration section below.

🤖 The Agentic Experience (No Docker/Code Engine Lingo Needed)

The true power of this MCP server is that you don't need to know Docker or Code Engine commands. You can simply state your goal, and the LLM will discover the environment, run the pipeline, and fix issues autonomously.

Here is an example interaction from a real session:

User:

"I have an app in the developer-splash folder. Deploy it to my Code Engine project."

Assistant's Autonomous Thought Process:

*Discovery:* "Let me check what projects and namespaces exist... Found project my-project and namespace my-namespace."
*Prerequisites:* "No pull secret in this project yet. I'll get the API key from the .env file and create the secret icr-pull-secret."
*Execution:* "Now I'll run the full pipeline: build → push → deploy → wait."
*Validation:* "It's deployed but stuck at 'deploying'. Let me check the logs... The container is running but the readiness probe is failing."
*Self-Correction:* "Ah, the sed pattern in the Dockerfile didn't match nginx alpine's default config format for port 80. I'll fix the Dockerfile with a regex-safe sed and rebuild."
*Completion:* "App is live! 🎉 Status: ready."

Assistant Response to User:

"Your app is deployed and live at: https://developer-splash. . .codeengine.appdomain.cloud. I had to fix a minor port configuration issue in your Dockerfile, but it is successfully running now!"

With this MCP server, the AI acts as an expert DevOps engineer pairing with you.

📊 MCP Activity Dashboard (v1.4.0)

See what your AI assistant is doing in real time — tool calls, idle gaps between steps, deploy outcomes, and live app URLs.

flowchart LR

A[MCP tool call] -->|MCP_ACTIVITY_ENABLED| B[events.jsonl] B --> C{Dashboard} C -->|VS Code extension| D[Activity tab] C -->|Browser| E[localhost:8767] D --> F[Deployments tab\ninventory + actions]

Activity logging (on by default)

Since v1.6.0 the server logs every tool start/finish to ~/.code-engine-mcp/activity/events.jsonl — input summaries, pipeline sub-steps (proc_build_push_deploy), result highlights, and optional HTTP smoke-test labels. API keys, passwords, TLS keys, env var values, and secret payloads are redacted. The file rotates at 5 MB.

Optional env in your MCP client config:

"MCP_ACTIVITY_ENABLED": "false",

"MCP_ACTIVITY_EVENTS_PATH": "/custom/path/events.jsonl", "MCP_ACTIVITY_SESSION_ID": "session:my-chat-001", "MCP_ACTIVITY_CHAT_LABEL": "Deploy Star Wars splash"

In the VS Code extension, turn logging off with codeEngineMcp.activityEnabled. Restart the MCP server after changing env.

See .env.example for all MCP_ACTIVITY_* variables.

Open the dashboard

Method	How
VS Code extension	Command Palette → IBM Code Engine MCP: Open MCP Activity Dashboard
Browser (dev repo)	`npm run dashboard` → http://localhost:8767/
Live refresh	On by default in the browser; toggle in-panel or set `codeEngineMcp.activityLiveRefresh` (extension)

The Activity tab shows a session timeline with tool duration, idle gaps, and a task-outcome banner (status, image, live URL). The Deployments tab lists projects and apps from Code Engine and supports get-details, redeploy, and delete via MCP tools.

Example chat prompt:

*"I have a Star Wars splash page in examples/starwars-splash. Deploy it to Code Engine using only MCP tools — build for linux/amd64, push to my ICR namespace, and deploy to my Code Engine project. Show me the live URL when ready."*

Open the Activity Dashboard while the assistant runs to watch proc_build_push_deploy progress step by step.

Deploy Your First App

This walks through deploying the included Star Wars splash page example — a static nginx container — entirely through the MCP server.

Apple Silicon users: always build with --platform linux/amd64. Code Engine runs amd64 only.

Step 1 — Build and push the image

cd examples/starwars-splash

podman build --platform linux/amd64 -t us.icr.io/ /starwars-splash:v1.0.0 . podman push us.icr.io/ /starwars-splash:v1.0.0

Or ask your assistant:

Build examples/starwars-splash as us.icr.io/my-namespace/starwars-splash:v1.0.0 for linux/amd64 and push it

MCP response — `build_container_image`:

"success": true, "command": "podman build --platform linux/amd64 -t us.icr.io/my-namespace/starwars-splash:v1.0.0 ...", "build_output": "STEP 1/5: FROM nginx:alpine\nSTEP 2/5: COPY index.html /usr/share/nginx/html/index.html\nSTEP 3/5: RUN sed -i 's/listen 80;/listen 8080;/g' /etc/nginx/conf.d/default.conf\nSTEP 4/5: EXPOSE 8080\nSTEP 5/5: CMD [\"nginx\", \"-g\", \"daemon off;\"]\nSuccessfully tagged us.icr.io/my-namespace/starwars-splash:v1.0.0" }

Note: Container runtimes (Podman/Docker) write build progress to stderr. The build_output field combines stdout and stderr so you see the full build log.

MCP response — `push_container_image`:

"success": true, "command": "podman push us.icr.io/my-namespace/starwars-splash:v1.0.0", "output": "Getting image source signatures\nCopying blobs...\nWriting manifest to image destination" }

Step 2 — Create a registry pull secret

Ask your assistant (once per project):

Create a registry secret called icr-pull-secret in project <project-id> for us.icr.io using my IBM Cloud API key

Or use the ce_create_secret tool directly:

"project_id": " ", "name": "icr-pull-secret", "format": "registry", "data": { "username": "iamapikey", "password": " ", "server": "us.icr.io", "email": "user@example.com" } }

MCP response — `ce_create_secret`:

"name": "icr-pull-secret", "format": "registry", "resource_type": "secret_registry_v2", "created_at": "2026-05-08T22:10:00Z", "project_id": " " }

Step 3 — Deploy the application

Ask your assistant:

Deploy us.icr.io/my-namespace/starwars-splash:v1.0.0 to Code Engine project <project-id>

as app "starwars-splash" using pull secret icr-pull-secret, min 1 instance

Or use the ce_create_application tool:

"project_id

只显示了开头部分；其余内容请在仓库中阅读

IBM Code Engine MCP Server

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“开发者工具”中的其他服务器比较i

常见问题

替代选择

GitHub

Desktop Commander

Cloudflare MCP

作者的 README

IBM Code Engine MCP Server

How It Works

✨ What You Get

🚀 Quick Start

2) Build the server

3) Run once to verify

🤖 The Agentic Experience (No Docker/Code Engine Lingo Needed)

📊 MCP Activity Dashboard (v1.4.0)

Activity logging (on by default)

Open the dashboard

Deploy Your First App

Step 1 — Build and push the image

Step 2 — Create a registry pull secret

Step 3 — Deploy the application