It could make sense to have some Reshapr features available as MCP endpoints OR - as Reshapr should be mainly used in a development situation - we could choose to provide SKILLS to do so....
I think of these features that would make sense being called by an agent:
Import a new specification to discover a new service - I don't think we should let it create a default configuration plan and all the bells and whistles from this one though...Attach a new artifact to attach a complementary artifact like a Prompts, Resources or CustomTools fileList available ServicesList available Gateway GroupsCreate a new Configuration Plan for a serviceList available Expositions to get the list of available services and endpoints
Some other tools, like the one around secrets, will probably be needed in the long run, but it might be too much for a start...
What do you think?
It could make sense to have some Reshapr features available as MCP endpoints OR - as Reshapr should be mainly used in a development situation - we could choose to provide SKILLS to do so....
I think of these features that would make sense being called by an agent:
Import a new specificationto discover a new service - I don't think we should let it create a default configuration plan and all the bells and whistles from this one though...Attach a new artifactto attach a complementary artifact like aPrompts,ResourcesorCustomToolsfileList available ServicesList available Gateway GroupsCreate a new Configuration Planfor a serviceList available Expositionsto get the list of available services and endpointsSome other tools, like the one around secrets, will probably be needed in the long run, but it might be too much for a start...
What do you think?