A web-based management interface for the Platform Provisioner by TIBCO®. Provides recipe management capabilities for platform provisioning and operational tasks. The UI is fully customizable and can be extended to fit your needs. By default, the UI is fit for the TIBCO Platform.
| Pipeline Management | Recipe Options |
|---|---|
 |
 |
- Recipe Management — Create, edit, and deploy provisioning recipes through an intuitive UI
- Kubernetes Integration — Direct integration with Kubernetes API for ConfigMap/Secret management and pipeline execution
- Multi-Cloud Provisioning — Zero-trust provisioning system for multi-cloud environments
- Self-Service — Enable developers to provision infrastructure and applications on demand
- SAML Authentication — Enterprise SSO support with SAML-based authentication
- MCP Server — Model Context Protocol server for AI-assisted pipeline management via Claude Code (details)
- Theme Support — Multiple built-in color themes
- Developer/DevOps engineers managing recipes for platform provisioning
- SRE teams managing recipes for operational tasks
- Platform teams providing self-service provisioning for developers
- Dynamic infrastructure and application deployment on demand
- Running Kubernetes cluster (Docker Desktop, GKE, EKS, etc.)
- Platform Provisioner deployed in the cluster
export PIPELINE_GUI_SERVICE_PORT=8080
export PIPELINE_GUI_SERVICE_TYPE=LoadBalancer
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/TIBCOSoftware/platform-provisioner/main/dev/platform-provisioner-install.sh)"Access http://localhost:8080/ to see the UI.
cd provisioner-webui
npm install
npm run dev # Start Vite dev server (port 5173)
npm run start:local # Build and start with backend server# Validate (typecheck + build)
make typecheck build
# Deploy to local Kubernetes
make deploy-local
# Run E2E tests
make test-e2eSee the provisioner-webui README for detailed development instructions.
The platform provisioner includes an MCP server that allows Claude Code to manage recipes and pipelines directly. Pipeline runs created via MCP are labeled with the individual user's identity (e.g., created-by: tao.peng).
-
Add the MCP server to Claude Code:
# Staging claude mcp add --transport http --scope user tibco-platform-provisioner https://provisioner-staging.cic2.tibcocloud.com/mcp # Production claude mcp add --transport http --scope user tibco-platform-provisioner https://provisioner.cic2.tibcocloud.com/mcp
-
On first MCP tool call, Claude Code triggers OAuth — complete SAML SSO login in the browser.
-
Start using MCP tools in Claude Code:
> list my pipeline runs > create a pipeline run using generic-runner for account gcp-123 > check pipeline run status for generic-runner-gcp-123-1779289409753
| Tool | Purpose |
|---|---|
whoami |
Current user identity |
listAccounts |
Accessible accounts |
listPipelines |
Available pipeline templates |
listPipelineRuns |
Pipeline runs (default: current user) |
createPipelineRun |
Create and run a pipeline |
getPipelineRun |
Pipeline run details and status |
stopPipelineRun / deletePipelineRun |
Stop or delete a run |
loadRecipe / saveRecipe |
Load or save recipe configurations |
getTaskRunDetails / getContainerLog |
Task details and container logs |
See docs/ai/mcp.md for full documentation including authentication flow, token lifecycle, troubleshooting, and deployment guide.
- Frontend: Vue 3, TypeScript, PrimeVue, Vite
- Backend: Node.js, Koa
- Testing: Playwright (E2E), Vitest (Unit)
- Deployment: Docker, Helm, Kubernetes
See CONTRIBUTING.md for guidelines.
See SECURITY.md for reporting vulnerabilities.
Copyright 2025 Cloud Software Group, Inc.
Licensed under the Apache License, Version 2.0. See the LICENSE file for details.