SHIP-0045: Add Shipwright MCP Server proposal document#287
Conversation
pull-request-size
bot
added
the
size/L
ayushsatyam146
force-pushed
the
shp-mcp-server
branch
from
31022c6 to
e025afe
Compare
Introduces a Model Context Protocol (MCP) server for Shipwright Build, enabling AI-assisted DevOps workflows and natural language interactions with Shipwright resources. Signed-off-by: Ayush Satyam <ayushsatyam146@gmail.com>
ayushsatyam146
force-pushed
the
shp-mcp-server
branch
from
e025afe to
6062443
Compare
adambkaplan
left a comment
adambkaplan
left a comment
There was a problem hiding this comment.
/approve
I think an MCP server for Shipwright makes sense as it will help make the project useful to AI agents. We can provide specific context through the MCP server that the general-purpose Kubernetes MCP server cannot. As a "provisional" SHIP, this proposal meets our design criteria for this phase.
Adding comments to help drive further conversation and get the proposal to "implementable".
My primary concern is contributor capacity. We are a pretty small community and have trouble maintaining some of our existing repositories already, like triggers. This would be another component that would need care, attention, and maintenance.
|
|
||
| ## Proposal | ||
|
|
||
| Introduce a new project `shipwright-io/mcp-server` (or integrate into the main build repository) that implements an MCP server exposing Shipwright Build operations as standardized tools. I recommend a seperate reposditory. |
There was a problem hiding this comment.
👍 - agree that MCP warrants a separate repository.
|
|
||
| ## Proposal | ||
|
|
||
| Introduce a new project `shipwright-io/mcp-server` (or integrate into the main build repository) that implements an MCP server exposing Shipwright Build operations as standardized tools. I recommend a seperate reposditory. |
There was a problem hiding this comment.
Typo nit (not blocking):
| Introduce a new project `shipwright-io/mcp-server` (or integrate into the main build repository) that implements an MCP server exposing Shipwright Build operations as standardized tools. I recommend a seperate reposditory. | |
| Introduce a new project `shipwright-io/mcp-server` (or integrate into the main build repository) that implements an MCP server exposing Shipwright Build operations as standardized tools. I recommend a seperate repository. |
|
|
||
| Instead of a dedicated MCP server, we could add natural language processing to the existing CLI. | ||
|
|
||
| **Pros**: Single tool, familiar interface |
There was a problem hiding this comment.
Also one less repository to manage!
| Instead of a dedicated MCP server, we could add natural language processing to the existing CLI. | ||
|
|
||
| **Pros**: Single tool, familiar interface | ||
| **Cons**: Requires LLM integration in CLI, doesn't integrate with IDE-based AI assistants |
|
|
||
| ## Open Questions | ||
|
|
||
| 1. Should the MCP server be deployed as a sidecar to the Shipwright controller or as a standalone deployment? |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
/lgtm On behalf of @hasanawad94 |
3 participants
Introduces a Model Context Protocol (MCP) server for Shipwright Build, enabling AI-assisted DevOps workflows and natural language interactions with Shipwright resources.
Changes
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes