Dynamic ingestion of mcp configuration/definition files (similar to ${HOME}/.bashrc.d/*)

I would like to have the ability to add/remove or enable/disable mcp configurations independent of one another.

I am unable to find a legitimate source to provide an explanation of ${HOME}/.bashrc.d/* - so, a brief explanation
Instead of having a single ${HOME}/.bashrc - you would create
${HOME}/.bashrc.d/Kubernetes and ${HOME}/.bashrc.d/PythonEnv (as 2 example) allowing you to update the Kubernetes profile and not modify the PythonEnv.

Or potentially similar to how apache vhosts are enabled in Ubuntu
harvester.conf -> ../sites-available/harvester.conf
place mcp configuration files in ${HOME}/.aws/amazonq/mcp-available/
with the ones to be used ${HOME}/.aws/amazonq/mcp-enabled/ symlinked back to source(s)

I believe if this is to be implemented, it would need to take in to consideration the following
https://github.com/aws/amazon-q-developer-cli/issues/1391