Tekton Results MCP server

This project provides a Model Context Protocol (MCP) server for accessing historical Tekton PipelineRun and TaskRun data stored in Tekton Results.

Tools

List Operations

pipelinerun_list – List PipelineRuns from Tekton Results with Filtering Options

• namespace: Namespace to list PipelineRuns from (string, optional, default: current kubeconfig namespace; use - for all namespaces)
• labelSelector: Label selector to filter PipelineRuns (string, optional, comma-separated key=value pairs)
• prefix: Name prefix to filter PipelineRuns (string, optional)
• limit: Maximum number of results to return (integer, optional, range: 1-200, default: 50)

taskrun_list – List TaskRuns from Tekton Results with Filtering Options

• namespace: Namespace to list TaskRuns from (string, optional, default: current kubeconfig namespace; use - for all namespaces)
• labelSelector: Label selector to filter TaskRuns (string, optional, comma-separated key=value pairs)
• prefix: Name prefix to filter TaskRuns (string, optional)
• limit: Maximum number of results to return (integer, optional, range: 1-200, default: 50)

Get Operations

pipelinerun_get – Get a specific PipelineRun by name or filters

• name: Name of the PipelineRun to get (string, optional)
• namespace: Namespace of the PipelineRun (string, optional, default: current kubeconfig namespace; use - for all namespaces)
• labelSelector: Label selector to filter PipelineRuns (string, optional, comma-separated key=value pairs)
• prefix: Name prefix to filter PipelineRuns (string, optional)
• uid: Exact PipelineRun UID (string, optional). Unique identifier in Tekton Results database. This is the most efficient way to find a specific run.
• output: Return format - json or yaml (string, optional, default: "yaml")
• selectLast: If true, automatically select the most recent match when multiple runs match the filters (boolean, optional, default: true). When false, returns an error if multiple matches are found. Useful because run names are not unique in Tekton Results history.

taskrun_get – Get a specific TaskRun by name or filters

• name: Name of the TaskRun to get (string, optional)
• namespace: Namespace of the TaskRun (string, optional, default: current kubeconfig namespace; use - for all namespaces)
• labelSelector: Label selector to filter TaskRuns (string, optional, comma-separated key=value pairs)
• prefix: Name prefix to filter TaskRuns (string, optional)
• uid: Exact TaskRun UID (string, optional). Unique identifier in Tekton Results database. This is the most efficient way to find a specific run.
• output: Return format - json or yaml (string, optional, default: "yaml")
• selectLast: If true, automatically select the most recent match when multiple runs match the filters (boolean, optional, default: true). When false, returns an error if multiple matches are found. Useful because run names are not unique in Tekton Results history.

Log Operations

pipelinerun_logs – Get logs for a PipelineRun

• name: Name of the PipelineRun to get logs from (string, optional)
• namespace: Namespace where the PipelineRun is located (string, optional, default: current kubeconfig namespace; use - for all namespaces)
• labelSelector: Label selector to filter PipelineRuns (string, optional, comma-separated key=value pairs)
• prefix: Name prefix to filter PipelineRuns (string, optional)
• uid: Exact PipelineRun UID (string, optional). Unique identifier in Tekton Results database. This is the most efficient way to find a specific run.
• selectLast: If true, automatically select the most recent match when multiple runs match the filters (boolean, optional, default: true). When false, returns an error if multiple matches are found. Useful because run names are not unique in Tekton Results history

... View full README on GitHub