Using MCP servers for dynamic values

[dferguson992]

There are several configuration options which may benefit from dynamic values. For example, dynamic image selection may benefit from using a JIT MCP call powered by Amazon Bedrock for example to determine the top 5 most recent images from a model server. Additionally, this could be a great way to pull from HuggingFace a list of the top 10 models matching a search query.

Lots of options, but fundamentally the core functionality should not be impeded if MCP components fail to start. Furthermore, MCP components should be directed and focused on a specific type of query.

Thoughts?

[gfuentes11]

I've dealt with the pain of deploying containers that fail because the base image was stale or had broken dependencies by the time it hit ECS/SageMaker. By that point you're debugging code you are just trying to start testing. Having MCP servers validate or fetch the latest known-good images before the Dockerfile is written would catch that class of problem much earlier. Even when using Kiro CLI to try to research the latest image you sometimes get bad results.

I wonder though about how everything requiring a new MCP. I have started seeing OpenAI start providing prompts (instructions) that have been validated to reproduce the code a user may want with assistance. May be something worth exploring maintaining a repository of instructions... i guess then you would have to tailor that to different CLI tooling.

I like the idea though! It would at the very least save me sometime in the future especially as these become more autonomous.

[dferguson992]

Agree, it's a slippery slope to have everything be populated by an MCP. I think for the class of inputs which are bounded, an MCP is overkill, but for unbounded inputs an MCP would be very nice to have.

What makes this difficult to scope now is there aren't many "unbounded" inputs in the current flow. There are several being scoped (i.e. image version, deployment targets to existing clusters/endpoints etc.). I think is the line in the sand for what should not be MCP'd

[dferguson992]

New PR adding this feature has been merged!
#80