tektoncd/mcp-server

git clone https://github.com/tektoncd/mcp-server.git && cd mcp-server
go build -mod=vendor -o bin/tekton-mcp-server ./cmd/tekton-mcp-server
Deploy to Kubernetes: KO_DOCKER_REPO=<registry> ko apply -R -f config/

Usage

• •Needs a Kubernetes cluster with Tekton Pipelines installed, plus a kubeconfig or in-cluster service account.
• •Confirm kubectl config current-context points at the intended cluster before running.
• •Run locally with -transport=stdio for subprocess clients or -transport=http -address=127.0.0.1:8080 for Streamable HTTP.
• •The HTTP transport has no auth or TLS built in — put an authenticating TLS-terminating proxy in front before exposing it.

Key features

• ✓List operations with namespace, prefix, and label-selector filters for pipelines, pipelineruns, tasks, taskruns, and stepactions.
• ✓Create/get/update/patch/delete operations on Pipeline, Task, PipelineRun, TaskRun, plus start/restart and get_taskrun_logs.
• ✓Artifact Hub integration to discover, install, and trigger community Tekton tasks and pipelines.
• ✓Supports both stdio and Streamable HTTP transports with Kubernetes manifests for in-cluster deployment.

Best for

Teams running Tekton Pipelines on Kubernetes who want AI agents to manage, trigger, and troubleshoot pipelines.

Caveats

• ⚠Under active development — test on a non-production cluster and review the access granted.
• ⚠The HTTP transport does not provide authentication or TLS; never expose it to an untrusted network directly.
• ⚠The server can create, patch, start, restart, and delete resources using its kubeconfig/service-account permissions — use a dedicated least-privilege identity.
• ⚠Included dev manifests grant cluster-wide permissions; review before use on a shared cluster.