Connect AI assistants to IBM Code Engine for project, app, build, job, and runtime operations.
Most developer tooling work still happens through a UI a human drives. IBM Code Engine MCP server moves it into the conversation instead. Connect AI assistants to IBM Code Engine for project, app, build, job, and runtime operations.
C -->|Container Tools| D[Docker / Podman] C -->|Registry Tools| E[IBM Container Registry\nus.icr.io] C -->|Code Engine Tools| F[IBM Code Engine\nREST API] C -->|Procedures| G[Multi-step Workflows]
The server publishes 8 tools. What each one is for:
MCP — ready setup for GitHub Copilot, Cline, Bob, Claude Desktop, and the optional VS Code extension in vscode-extension/Started — at timestampLegacy — ?apiKey= query parameterMethod — HowProtocol — MethodMessaging — POSTFetch — npx -y @tokenizin/mcp-npx-fetchFilesystem — npx -y @modelcontextprotocol/server-filesystem /dataBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: MCP_ACTIVITY_ENABLED, MCP_ACTIVITY_EVENTS_PATH, MCP_ACTIVITY_SESSION_ID, MCP_ACTIVITY_CHAT_LABEL, IBMCLOUD_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. IBM Code Engine's toolset — MCP, Started, Legacy and 5 more — is a fair guide to whether it matches your workflow. It is maintained by markusvankempen; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| MCP | ready setup for GitHub Copilot, Cline, Bob, Claude Desktop, and the optional VS Code extension in vscode-extension/ |
| Started | at timestamp |
| Legacy | ?apiKey=<key> query parameter. |
| Method | How |
| Protocol | Method |
| Messaging | POST |
| Fetch | npx -y @tokenizin/mcp-npx-fetch |
| Filesystem | npx -y @modelcontextprotocol/server-filesystem /data |
{
"mcpServers": {
"fetch": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp-fetch-server.<subdomain>.<region>.codeengine.appdomain.cloud/sse"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MCP_ACTIVITY_ENABLED | Configuration value read at startup. | Optional |
| MCP_ACTIVITY_EVENTS_PATH | Filesystem location the server is allowed to use. | Optional |
| MCP_ACTIVITY_SESSION_ID | Configuration value read at startup. | Optional |
| MCP_ACTIVITY_CHAT_LABEL | Configuration value read at startup. | Optional |
| IBMCLOUD_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.