Is this a new feature, an improvement, or a change to existing functionality?

New Feature

How would you describe the priority of this feature request

High

Please provide a clear description of problem this feature solves

The current MCP client tool wrapper requires a MCP server that operates over http with SES. Many MCP servers only provide documentation for running the stdio variant.

To alleviate this, the toolkit provides some documentation on using mcp_proxy to proxy requests from a stdio mcp server to a ses endpoint. Unfortunately, this documentation does not work for many MCP servers.

The default documentation creates a mcp_proxy run script that uses mcp-proxy uvx run service-name, but many MCP servers are not compatible with the rum command uvx run. Some require docker run commands, which are seemingly not compatible with mcp_proxy.

As an example, the new github mcp server recommends a docker run command:

https://github.com/github/github-mcp-server

Describe your ideal solution

It would be a lot more straightforward if the mcp_tool_wrapper could accept and interact with a stdio running service, or even better would be if you could drop in the VS code / Cursor MCP configuration verbatim somewhere into AIQ and have it "just work", as most of these servers provide that documentation and little else.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct
• I have searched the open feature requests and have found no duplicates for this feature request