The tekton toolset adds Tekton-specific helpers on top of the generic Kubernetes resource tools.
Enable it with:
kubernetes-mcp-server --toolsets core,config,tektontekton_pipeline_startstarts a Pipeline by creating a PipelineRun.tekton_pipelinerun_lifecyclerestarts a PipelineRun from its existing spec or cancels it by settingspec.statustoCancelled.tekton_pipelinerun_logscollects logs from TaskRuns owned by a PipelineRun.
tekton_task_startstarts a Task by creating a TaskRun.tekton_taskrun_restartcreates a new TaskRun from an existing TaskRun spec.tekton_taskrun_logsresolves a TaskRun pod and returns step/sidecar logs.
Pipeline-as-Code Repository and operator TektonConfig resources are ordinary Kubernetes resources; use resources_list and resources_get for those.
List Pipeline-as-Code repositories in a namespace with resources_list:
{"apiVersion":"pipelinesascode.tekton.dev/v1alpha1","kind":"Repository","namespace":"my-namespace"}Get the usual cluster TektonConfig with resources_get:
{"apiVersion":"operator.tekton.dev/v1alpha1","kind":"TektonConfig","name":"config"}These tools are read-only except the start and lifecycle operations.
Use the pipeline-troubleshoot prompt with namespace and name to gather PipelineRun status, related TaskRuns, logs, events, Pipeline-as-Code repositories, and TektonConfig context into one diagnostic prompt.