Deploy Your App

IMPORTANT
Adobe LLM Apps is currently in Beta.
Features, workflows, and UI shown here do not necessarily represent the final state of the product. To join the Beta, send an email to llm-apps-beta@adobe.com.

Once you have written your handler code and pushed it to your linked repository, you can deploy the app from the LLM Apps UI.

Start the deployment

Navigate to the App Detail page. Click the Deploy button in the top-right corner:

App Detail — ready to deploy

This opens the deployment dialog. Select the target environment from the dropdown:

Deploy dialog — select target environment

Click Deploy to start the pipeline. The four steps are:

  1. Gather credentials — reads app metadata, generates a GitHub token, and fetches Runtime credentials from Console API.
  2. Trigger build pipeline — sends all parameters to the build pipeline.
  3. Clone and build — the pipeline clones your repository, generates actions.json from the UI metadata, runs npm install and webpack to produce dist/index.js.
  4. Deploy to Runtime — deploys the bundle to your app’s Adobe I/O Runtime namespace.

Once started, the pipeline runs automatically and shows real-time progress:

Deploy pipeline running

NOTE
If an action has metadata in the UI but no matching handler file in the repository, it is still registered. Invocations use a default stub handler until you add the real code.

After a successful deployment

When all steps complete, the dialog shows a Deploy successful confirmation with the deployed URL and artifact details:

Deploy successful

Click Close to dismiss the dialog. Scroll down to the Test the app section on the App Detail page:

Test the app — deployed URLs

Each environment (Staging and Production) shows the MCP server URL on Adobe I/O Runtime. This is the URL you provide to the LLM platform when registering your app. Click Copy URL to copy it to your clipboard.

The Deployment history section below keeps a full log of every deployment across environments:

Deployment history

Each row shows the target Environment (Stage or Production), Status (Success or Failed), and the Deployed at date. You can use this table to track when deployments happened and verify that the
latest deployment succeeded.

recommendation-more-help
llm-apps-help-main-toc