Tekton Model Context Protocol server

Tekton MCP Server exposes Tekton resources to Model Context Protocol (MCP) clients. It currently focuses on tektoncd/pipeline and supports both stdio and Streamable HTTP transports.

[!IMPORTANT] This project is under active development. Test it in a non-production cluster and review the access granted to both the server and the connected MCP client.

Prerequisites

The server needs:

• access to a Kubernetes cluster with Tekton Pipelines installed
• a kubeconfig for local use, or an in-cluster service account when deployed to Kubernetes
• Go at the version in go.mod when building from source

kubectl and ko are also required to deploy the manifests from a source checkout.

Build from source

git clone https://github.com/tektoncd/mcp-server.git
cd mcp-server
mkdir -p bin
go build -mod=vendor -o bin/tekton-mcp-server ./cmd/tekton-mcp-server

The server uses the standard Kubernetes client configuration. Confirm that kubectl config current-context points to the intended cluster before running it.

Run locally

stdio

Use stdio when an MCP client starts the server as a subprocess:

./bin/tekton-mcp-server -transport=stdio

A typical MCP client entry looks like this; adapt the surrounding configuration to the client being used:

{
  "mcpServers": {
    "tekton": {
      "command": "/absolute/path/to/bin/tekton-mcp-server",
      "args": ["-transport=stdio"]
    }
  }
}

Streamable HTTP

Bind to localhost for local development:

./bin/tekton-mcp-server -transport=http -address=127.0.0.1:8080

Connect the MCP client to http://127.0.0.1:8080.

Deploy to Kubernetes

Set KO_DOCKER_REPO to a registry accessible to the cluster, then build the image and apply the manifests:

export KO_DOCKER_REPO=registry.example.com/YOUR-USER/mcp-server
ko apply -R -f config/
kubectl -n tekton-mcp rollout status deployment/tekton-mcp-server

For local access to the in-cluster service:

kubectl -n tekton-mcp port-forward service/tekton-mcp-server 8080:8080

ko delete -R -f config/ removes every included resource, including the tekton-mcp namespace and anything else stored in that namespace. Use it only when that destructive cleanup is intended.

Compatibility

The server uses Tekton v1 resources and is built and tested against the Kubernetes, Tekton Pipelines, and MCP Go SDK versions recorded in go.mod. Until a broader compatibility matrix is published, test the server with the exact cluster versions on which it will run.

Security

The server can read and modify Tekton resources using the permissions of its