Tektoncd Model Context Protocol server

What is Tektoncd Model Context Protocol server?

This project provides a Model Context Protocol (MCP) server for the tektoncd projects, initially focusing on tektoncd/pipeline objects such as Pipelines, PipelineRuns, Tasks, TaskRuns, and StepActions. It will add support for other tektoncd projects over time. The server is intended for users who want to manage Tekton resources programmatically through an MCP-compatible client.

How to use Tektoncd Model Context Protocol server?

The README does not include explicit installation or configuration instructions. The server exposes a set of tools (functions) that can be invoked via an MCP client. Each tool requires parameters such as a namespace, resource name, or YAML definition. No specific command line or configuration key is mentioned.

Key features of Tektoncd Model Context Protocol server

• List Tekton resources with filtering by namespace, name prefix, and label selector.
• Create, get, update, patch, delete, start, and restart Pipelines, Tasks, PipelineRuns, TaskRuns.
• Fetch logs from a specific TaskRun.
• Integrate with Artifact Hub to discover, install, and trigger community tasks and pipelines.
• Output for get operations in JSON or YAML format.

Use cases of Tektoncd Model Context Protocol server

• Automate Tekton pipeline management without direct kubectl usage.
• Programmatically create, inspect, and delete pipeline or task runs in a Kubernetes cluster.
• Discover and install community-maintained tasks and pipelines from Artifact Hub.
• Trigger or restart a pipeline run or task run from an MCP-enabled assistant.

FAQ from Tektoncd Model Context Protocol server

What Tekton resources does the server currently support?

The server initially supports tektoncd/pipeline objects: Pipelines, PipelineRuns, Tasks, TaskRuns, and StepActions. Support for other tektoncd projects will be added over time.

How can I filter resources when listing?

List operations accept an optional prefix parameter for name filtering and an optional label-selector parameter. List operations for PipelineRuns and TaskRuns also support a field-selector.

Can I install tasks and pipelines from the community catalog?

Yes. The server integrates with Artifact Hub to search for tasks and pipelines, install them by package ID and version, and trigger them with parameters.

How do I get logs from a TaskRun?

Use the get_taskrun_logs tool. It requires the name of the TaskRun and an optional namespace (default: “default”).

What output formats are available for get operations?

For get_pipeline, get_task, get_pipelinerun, and get_taskrun, you can specify output as either “json” or “yaml” (default: “yaml”).