IBM Code Engine MCP Server

Read from the package source without running it. The installed server may list more.

• build_container_image

  Build a container image using Docker or Podman

• ce_create_applicationwrite action

  Create a Code Engine application from a container image

• ce_create_bindingwrite action

  Create a service binding to connect an IBM Cloud service instance to a Code Engine component

• ce_create_config_mapwrite action

  Create a configmap in a Code Engine project

• ce_create_domain_mappingwrite action

  Map a custom domain to a Code Engine application. Requires a TLS secret created with ce_create_tls_secret_from_pem. The domain CNAME must point to custom.<subdomain>.us-south.codeengine.appdomain.cloud (returned by this call).

• ce_create_jobwrite action

  Create a job definition in Code Engine

• ce_create_job_runwrite action

  Submit a job run from an existing job definition

• ce_create_projectwrite action

  Create a new Code Engine project

• ce_create_secretwrite action

  Create a secret in a Code Engine project (generic, registry, ssh_auth, etc.)

• ce_create_tls_secret_from_pemwrite action

  Create a TLS secret in Code Engine by reading certificate and key PEM files from disk. Use this after obtaining a cert with certbot. The cert and key are read from the given file paths and stored as a Code Engine secret of format "tls".

• ce_delete_applicationwrite action

  Delete a Code Engine application

• ce_delete_bindingwrite action

  Delete a service binding from a Code Engine project

• ce_delete_config_mapwrite action

  Delete a configmap from a Code Engine project

• ce_delete_domain_mappingwrite action

  Delete a custom domain mapping from a Code Engine project

• ce_delete_jobwrite action

  Delete a Code Engine job definition

• ce_delete_projectwrite action

  Delete a Code Engine project

• ce_delete_secretwrite action

  Delete a secret from a Code Engine project

• ce_get_app_instance

  Get status details for a specific running instance of a Code Engine application

• ce_get_app_logs

  Get logs for a Code Engine application. Retrieves logs from all running pods (or a specific instance) via the Code Engine Kubernetes API proxy.

• ce_get_app_revision

  Get details of a specific revision of a Code Engine application

• ce_get_application

  Get details of a Code Engine application

• ce_get_binding

  Get details of a specific service binding in a Code Engine project

• ce_get_config_map

  Get details of a specific configmap in a Code Engine project

• ce_get_domain_mapping

  Get details of a specific custom domain mapping

• ce_get_job

  Get details of a specific Code Engine job definition

• ce_get_job_runwrite action

  Get status and details of a job run

• ce_get_project

  Get details of a specific Code Engine project

• ce_get_project_status

  Get the status details of a Code Engine project (readiness, enabled components, etc.)

• ce_get_secret

  Get metadata for a specific secret (keys only, no values)

• ce_list_app_instances

  List all running instances (pods) of a Code Engine application

• ce_list_app_revisions

  List all revisions (deployed versions) of a Code Engine application

• ce_list_applications

  List applications in a Code Engine project

• ce_list_bindings

  List all service bindings in a Code Engine project (bindings connect IBM Cloud services to apps/jobs)

• ce_list_config_maps

  List configmaps in a Code Engine project

• ce_list_domain_mappings

  List all custom domain mappings in a Code Engine project

• ce_list_egress_ips

  List the public egress IP addresses used by a Code Engine project (useful for allowlisting in firewalls)

• ce_list_job_runs

  List job runs in a Code Engine project

• ce_list_jobs

  List job definitions in a Code Engine project

• ce_list_projects

  List all Code Engine projects across all or a specific region

• ce_list_secrets

  List secrets in a Code Engine project

• ce_refresh_icr_pull_secret

  Refresh a Code Engine registry pull secret for IBM Container Registry (ICR) using the server's own IBM Cloud API key. Automatically deletes the existing secret and recreates it with fresh credentials. Use this when deployments fail with "no_revision_ready" or "unknown" status — a common cause is a stale or expired ICR pull secret. No API key input required — the server uses its own IBMCLOUD_API_KE

• ce_renew_tls_secret_from_pem

  Renew an existing TLS secret in Code Engine by reading updated PEM files from disk. Use this when a Let's Encrypt cert has been renewed (every 90 days). Updates the secret in-place — no need to delete and recreate or update domain mappings.

• ce_update_applicationwrite action

  Update an existing Code Engine application (image, scaling, etc.)

• ce_update_config_mapwrite action

  Update an existing Code Engine configmap (PATCH)

• ce_update_domain_mappingwrite action

  Update an existing Code Engine custom domain mapping (PATCH) — e.g. change the target app

• ce_update_jobwrite action

  Update an existing Code Engine job definition (PATCH)

• ce_update_secretwrite action

  Update an existing Code Engine secret in-place (PATCH). Use ce_renew_tls_secret_from_pem for TLS cert renewal. For generic secrets supply a data object with the new key/value pairs.

• ce_wait_for_app_ready

  Poll a Code Engine application until its status becomes "ready" or a timeout is reached. Returns immediately when ready. Useful after ce_create_application or ce_update_application to confirm the new revision is live.

• detect_container_runtime

  Detect available container runtime (Docker or Podman)

• iam_get_token_info

  Get information about the current IBM Cloud IAM token — account ID, subject, expiry time, and remaining validity. Useful for diagnosing authentication failures without exposing the token itself.

• icr_create_namespacewrite action

  Create a new namespace in IBM Container Registry. Required before pushing images for the first time. Uses the ICR REST API with your IBM Cloud API key.

• icr_delete_imagewrite action

  Delete an image from IBM Container Registry (ICR) by tag or digest

• icr_list_images

  List images in IBM Container Registry (ICR)

• icr_list_namespaces

  List IBM Container Registry (ICR) namespaces in your account

• inspect_container_image

  Inspect a local container image — shows architecture, labels, environment variables, entrypoint, exposed ports, and layer count

• list_local_images

  List all local container images

• login_to_registry

  Log in to a container registry (e.g. IBM Container Registry) so images can be pushed/pulled. Uses IBM Cloud IAM token for ICR or username/password for other registries.

• proc_build_push_deploywrite action

  PROCEDURE: Full container pipeline in one step — auto-detects Podman or Docker, builds for linux/amd64, pushes to IBM Container Registry (ICR), creates or updates a Code Engine application, waits for ready, and returns the public URL. Accepts a project name or ID. Builds the full ICR image path from namespace + app name + tag so you do not need to know ICR URLs. When PROVENANCE_ENABLED=true, emits

• proc_setup_custom_domain

  PROCEDURE: Custom domain setup in one step — reads TLS certificate PEM files from disk (e.g. from certbot/Let's Encrypt), creates a TLS secret in Code Engine, then creates the domain mapping. Returns the CNAME target value to add in your DNS provider.

• prune_imageswrite action

  Remove unused/dangling container images to reclaim disk space. By default removes only dangling images; use all=true to remove all unused images.

• push_container_image

  Push container image to registry

• remove_local_imagewrite action

  Remove a local container image to free disk space

• tag_container_image

  Tag a local container image with a new name/tag — useful to retag before pushing to ICR

• test_container_locallywrite action

  Run container locally for testing

• write_or_modify_filewrite action

  Write or update a text file in the workspace. Returns bytes written and content hash.

• Code scan33 source files scanned13/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 84 days ago12/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

60/100

higher than 14% of 1,119 Developer tools servers

Tools

65

the typical Developer tools server has 7

Tools that change things

45%

typical: 5%. Fewer write tools means less an agent can break

Downloads a week

69

more than 48% of 436 Developer tools servers with a package

IBM Code Engine MCP Server: common questions

Is IBM Code Engine MCP Server safe?

With care: it is graded C, so read the findings first (60/100). Read the IBM Code Engine MCP Server safety report

How do I install IBM Code Engine MCP Server?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does IBM Code Engine MCP Server need an API key?

Yes. The registry entry asks for IBMCLOUD_API_KEY.

Is IBM Code Engine MCP Server maintained?

The last commit was 123 days ago (2026-07-04). The latest release is v1.4.2.

What can I use instead of IBM Code Engine MCP Server?

Servers from other publishers that do the same job: walkerOS Flow MCP server, Omnara MCP server and Metaplex Agent Registry MCP server.

How does IBM Code Engine MCP Server compare with other Developer tools MCP servers?

safety score 60/100 (higher than 14% of 1,119 Developer tools servers); tools 65 (the typical Developer tools server has 7); tools that change things 45% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.