AWS Q CLI Zsh setting

 

If you want to pull in your local .zshrc settings for each shell launch, you can follow the following steps:

1. copy the following content to a new file named "myzsh" and put it somewhere in your local bin folder. I put it under ~/bin/myzsh

#!/bin/zsh
# More robust wrapper that handles -c flag properly
if [[ "$1" == "-c" ]]; then
    source ~/.zshrc
    eval "$2"
else
    # Fallback to regular zsh behavior
    exec zsh "$@"
fi

2.

chmod +x ~/bin/myzsh
export AMAZON_Q_CHAT_SHELL="$HOME/bin/myzsh"

And use q chat as you normally do. in my case, it was able to see all the aliases I defined in my .zshrc file while before doing this it couldn't see them.

How to decouple MCP servers from the MCP clients.

You can easily decoulple your MCP servers from your MCP clients with the existing stdio <-> tcp tool, such as ncat (which is part of the nmap tool). Without any code changes to the existsing MCP servers available, you can serve them on a TCP port. For example, this is how I run the filesystem MCP server

ncat -lkp 7002 -e "/usr/local/bin/npx -y @modelcontextprotocol/server-filesystem /tmp"

On the mcp client side (such as Claude desktop or Cline), you would simply run another ncat as client to connect to the server

ncat 127.0.0.1 7002

That’s all. now you are serving MCP server over the network. Of course you can run multiple MCP servers on different ports.

on MacOS, you can install nmap with brew: brew install nmap