tekton-results-mcp-server

enarha/tekton-results-mcp-server

3.2

If you are the rightful owner of tekton-results-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.

MCP Server for Tekton Results is designed to facilitate the management and retrieval of pipeline execution results in Tekton, a Kubernetes-native CI/CD framework.

tekton-results-mcp-server

MCP Server for Tekton Results

Available tools

The server exposes read-only tools for PipelineRuns and TaskRuns inside a Tekton Results deployment:

  • pipelinerun_list / taskrun_list – return JSON summaries filtered by namespace, label selectors, name prefixes, and result count limits.
  • pipelinerun_describe / taskrun_describe – fetch a single run and emit the full resource in YAML (default) or JSON.
  • pipelinerun_logs / taskrun_logs – stream stored logs for completed runs.

The filters mirror Tekton Results behavior:

  • namespace: defaults to the current kubeconfig namespace; use - to search all namespaces.
  • labelSelector: comma separated key=value pairs.
  • prefix: run name prefix.
  • limit (list only): cap returned items between 1 and 200.

All tools rely on the in-cluster or kubeconfig context used to start the MCP server, so no additional Tekton Results credentials are required. When running outside the cluster, ensure the kubeconfig context has access to the Tekton Results aggregated API.

Direct Tekton Results access

If your cluster does not expose the aggregated API (for example when you port-forward tekton-results-api-service), set the following environment variables before starting the MCP server:

  • TEKTON_RESULTS_BASE_URL: Base host for the API server (e.g. https://localhost:8443). The MCP server automatically appends /apis/results.tekton.dev/v1alpha2.
  • TEKTON_RESULTS_BEARER_TOKEN: Optional bearer token to authenticate against the Tekton Results API. If omitted, the token from your kubeconfig is used.
  • TEKTON_RESULTS_INSECURE_SKIP_VERIFY: Set to true when using self-signed certificates (for example, with port-forwarded services).

When these variables are not set, the MCP server communicates with Tekton Results through the Kubernetes aggregated API endpoint (/apis/results.tekton.dev).