Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"shipwright-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server for the Shipwright Build project. This server provides tools for interacting with Shipwright Build resources including Builds, BuildRuns, BuildStrategies, and ClusterBuildStrategies.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools
Manage Supabase projects — databases, auth, storage, and edge functions
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
MCP Security Weekly
Get CVE alerts and security updates for Shipwright Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server for the Shipwright Build project. This server provides tools for interacting with Shipwright Build resources including Builds, BuildRuns, BuildStrategies, and ClusterBuildStrategies.
This MCP server exposes Shipwright Build functionality through standardized tools that can be consumed by MCP clients. It's designed to work with the Shipwright Build Kubernetes-native CI/CD framework for building container images from source code.
go build -o shipwright-build-mcp-server main.go
The server runs as a standard MCP server over stdin/stdout. You can use it with any MCP client.
./shipwright-build-mcp-server
Refer config.example.json in the root of this project
list_builds – List Builds in a Namespace with Filtering Optionsnamespace: Namespace to list builds from (string, required)prefix: Name prefix to filter builds (string, optional)label-selector: Label selector to filter builds (string, optional)get_build – Get a Specific Build by Namename: Name of the build to get (string, required)namespace: Namespace where the build is located (string, optional, default: "default")create_build – Create a New Build Resourcename: Name of the build to create (string, required)namespace: Namespace where the build will be created (string, optional, default: "default")source-type: Source type - "Git" or "OCI" (string, required)source-url: Source URL (Git repository or OCI image) (string, required)context-dir: Context directory within the source (string, optional)revision: Git revision (branch, tag, or commit SHA) (string, optional)strategy: Build strategy name (string, required)strategy-kind: Build strategy kind - "BuildStrategy" or "ClusterBuildStrategy" (string, optional, default: "ClusterBuildStrategy")output-image: Output container image reference (string, required)parameters: Build parameters as key-value pairs (object, optional)timeout: Build timeout duration, e.g. "30m", "1h" (string, optional)delete_build – Delete a Build Resourcename: Name of the build to delete (string, required)namespace: Namespace where the build is located (string, optional, default: "default")list_buildruns – List BuildRuns in a Namespace with Filtering Optionsnamespace: Namespace to list buildruns from (string, required)prefix: Name prefix to filter buildruns (string, optional)label-selector: Label selector to filter buildruns (string, optional)get_buildrun – Get a Specific BuildRun by Namename: Name of the buildrun to get (string, required)namespace: Namespace where the buildrun is located (string, optional, defa